how to reboot all bricks safely and seamlessly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

If you need to reboot all bricks in a volume, what's the best way to do
this seamlessly?

I did this a few days ago by rebooting one, then waiting for "gluster
volume info" on another brick to show it back online before doing the
next, and so on. However, it went a bit wrong and I ended up with a
corruption. It fixed itself after a while, but because the system then
had a backlog of stuff to catch up with, it didn't fix itself for about
a day.

I wonder that I didn't leave enough time for the freshly rebooted brick
to apply all of the updates to itself that happened while it was
rebooting. So, what's the best way to find out whether a brick has fully
synced itself with the other bricks, before rebooting the next one?

I need to avoid having to shut the volume down as it would cause a
service outage.

Cheers,
Kingsley.

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users



[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux