Re: Replication logic

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

 



> Just take the slow brick offline during the initial sync 
> and then bring it online. The heal will go in background, 
> while the volume stays operational.

Yes, but the heal will then take three weeks. I have the data
at hand, so if can preload it with the trick I described,
I would have a full volume in a matter of a few hours instead.

> Have you thought for a 'replica 3' volume with a thin arbiter 
> being in the slow location ? 

Yes, I have pondered back and fro on this subject. I finally
opted for three full replicas because my underlying problems
of unreliability (flakey connections, the dynamic public
IP address of one of the peers) outweigh my desire for speed
and bandwidth conservation. To put it simply, a 2+1 volume
would make it easier and faster to store the data, but it
would make it harder to access it when one of the peers fails.

Z

________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.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