No active sinks for performing self-heal on file

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

 



On 05.08.2013 13:42, Pranith Kumar Karampuri wrote:
> Rebooting the servers like this can cause split-brains.
> Example:
> there is a volume with two bricks brick-A on server-A, and brick-B on 
> server-B.
> Lets say server-A is brought down and while it is down file-1 is
> modified which needs to be healed to server-A from server-B as soon as
> it is up.
> Now as soon as server-A is up lets say server-B is brought down
> before the healing on file-1 could complete. Now lets say file-1 is
> modified again.
> Now when server-B comes backup, file-1 would be in split-brain.
> 
> So make sure the files are healed after a server is brought up then
> only reboot the other machine.

Understood!

Would you recommend as best practice healing all the volumes after boot 
time (from rc.local or some custom init script)?

-- 
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro


[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