geo-replication master is distributed-replicated, slave is distributed only?

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

 



I’d like to have a distributed-replicated master volume, and distributed-only slave.

Can this be done?  Just beginning the research, but so far I’ve only done geo-replication with distributed-only volumes.  Tips/caveats on this kind architecture are welcome.

The rationale is straightforward—the master volume should be able to stay available with all data when suffering a node loss, but the geo-replicated volumes can be taken offline for repairs and resync as soon as possible.

Cheers,
Christian
_______________________________________________
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