Currently, when using zone routing, clients will write the number of
preferred/required times to all zones. This can be very costly on bandwidth
when zones are actual geographical zones (data center to data center).
A solution to this would be to add more logic to the server side and give the
client the option to only write to its local zone. The first server written to
in the local zone can be responsible for updating one node in each of the other
zones. The one server that gets the write in each of the other zones can be
responsible for updating its peers within that zone. This way a client can
satisfy its write preference/requirement only within its local zone and one
single write can propagated per zone.
Original issue reported on code.google.com by dremlok on 6 Apr 2011 at 7:40
Original issue reported on code.google.com by
dremlok
on 6 Apr 2011 at 7:40