Hi, if you simply reboot or shutdown one of the gluster nodes, there might be a (short or medium) unavailability of the volume on the nodes. To avoid this there's script: /usr/share/glusterfs/scripts/stop-all-gluster-processes.sh (path may be different depending on distribution) If i remember correctly: this notifies the clients that this node is going to be unavailable (please correct me if the details are wrong). If i do reboots of one gluster node, i always call this script and never have seen unavailability issues on the clients. Regards, Hubert Am Mo., 15. Juni 2020 um 19:36 Uhr schrieb ahemad shaik <ahemad_shaik@xxxxxxxxx>: > > Hi There, > > I have created 3 replica gluster volume with 3 bricks from 3 nodes. > > "gluster volume create glustervol replica 3 transport tcp node1:/data node2:/data node3:/data force" > > mounted on client node using below command. > > "mount -t glusterfs node4:/glustervol /mnt/" > > when any of the node (either node1,node2 or node3) goes down, gluster mount/volume (/mnt) not accessible at client (node4). > > purpose of replicated volume is high availability but not able to achieve it. > > Is it a bug or i am missing anything. > > > Any suggestions will be great help!!! > > kindly suggest. > > Thanks, > Ahemad > > ________ > > > > Community Meeting Calendar: > > Schedule - > Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC > Bridge: https://bluejeans.com/441850968 > > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > https://lists.gluster.org/mailman/listinfo/gluster-users ________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
