question on AFR behavior when master is down

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

 



Every so often it is necessary to bring machines down for some type of maintenance. If the machine is part of a glusterfs AFR replication setup what will happen in the following scenarios?:

master (brick1) is brought down, files are added, changed and deleted on glusterfs, master is brought back up. Does the master(brick1) resume it's master role? If so, does it sync and correctly add/chg/del files to its brick that were modified while it was down?

slave (brick3) is brought down, files are added, changed and deleted on glusterfs, slave is brought back up. Since the cluster had a slave removed from the middle of the order the replication specified in the config may change on other bricks I assume during the down time. Does this all get straightened out when this slave returns to the cluster? In other words I may replicate over the first three bricks for some files therefore while brick3 is down brick4 would actually become the third brick in the cluster then. Would it be receiving the replication intended for brick3? Again, when brick3 restarts does this all get straightened out. In other words, does brick4 get cleaned up and unintended files removed that were replicated to it when brick3 was down?






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

  Powered by Linux