The documenation I saw talked about multi-zones, but seems to stop in the details at 2 zones whereas, before, Jewel's Master zone(RW) wrote to Slave Zone(RO), and now after Jewel, writing to the Slave is doable (implying RW) to either zone. and didn't address the case of 3 or more zones. I thought the Master/Slave architecture implied it was limited to 2 zones. Is RW to any zone supported in 3+ zone configurations? The whole master/slave idea doesn't seem to make sense when talking about 3+ zones. I'm taking a guess that this must be fully meshed, and RW to any modifications in one zone replicates to *all* other zones (independent on the number of replicas specified in any cluster) If this is supported, what happens if zone1 data is modified, while at the same time a zone2 modifies the same data but the data was not yet copied from the zone1 to zone2. How is this conflict handled? Does last write win? Is the RADOS "primary copy", "Chain", and "Splay" replication strategy also used in multisite traffic? -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
