Hi Carl, Did you check for any pending heals before rebooting the gluster server? Also, it was discussed that shutting down the node, does not stop the bricks properly and thus the clients will eait for a timeout before restoring full functionality. You can stop your glusterd and actually all processes by using a script in /usr/share/gluster/scripts (the path is based on memory and could be wrong). Best Regards, Strahil NikllovOn Aug 19, 2019 18:34, Carl Sirotic <csirotic@xxxxxxxxxxxxxxxxxxxx> wrote: > > Hi, > > we have a replicate 3 cluster. > > 2 other servers are clients that run VM that are stored on the Gluster > volumes. > > I had to reboot one of the brick for maintenance. > > The whole VM setup went super slow and some of the client crashed. > > I think there is some timeout setting for KVM/Qemu vs timeout of > Glusterd that could fix this. > > Do anyone have an idea ? > > The whole point of having gluster for me was to be able to shut down one > of the host while the vm stay running. > > > Carl > > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > https://lists.gluster.org/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
