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??? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20200615/bb930b4b/attachment.html>
Karthik Subrahmanya
2020-Jun-16 04:39 UTC
[Gluster-users] Issues with replicated gluster volume
Hi Ahemad, Please provide the following info: 1. gluster peer status 2. gluster volume info glustervol 3. gluster volume status glustervol 4. client log from node4 when you saw unavailability Regards, Karthik On Mon, Jun 15, 2020 at 11:07 PM ahemad shaik <ahemad_shaik at yahoo.com> wrote:> 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 at gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20200616/40a8726c/attachment.html>
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 at yahoo.com>:> > 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 at gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-users
mount with -o backup-volfile-servers=<volfile_server2>:<volfile_server3> On Mon, Jun 15, 2020 at 1:36 PM ahemad shaik <ahemad_shaik at yahoo.com> wrote:> 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 at gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20200616/e8fa7885/attachment.html>