[GitHub] [couchdb] wohali commented on issue #2386: CouchDB Zones: How to verify if zones are setup correctly?

[GitBox <gi...@apache.org>]

wohali commented on issue #2386: CouchDB Zones: How to verify if zones are setup correctly?
URL: https://github.com/apache/couchdb/issues/2386#issuecomment-572732823
 
 
   @nicknaychov No, this is not correct:
   
   > Thus I think optimal solution would be using DB placement with two replicas hosted on 2 nodes in the local site and 1 on remote site node. This way I think will achieve that R/W will occur only on the local site(if both nodes are up) and avoid unnecessary WAN delays, while in case of emergency I will have backup.
   
   Every attempt to read or write will always attempt to access all replicas of a given database shard. Even if 2 of those 3 responses arrive locally and result in a faster response to the client, you still have all traffic for every request transitting your WAN.
   
   As @kocolosk said, your best approach is to use a standard main 3-node cluster (1 zone), then use standard CouchDB replication to keep your offsite backup current. You can run these replications on that backup cluster (i.e. "pull" replication) to keep load on the main cluster light.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services