[GitHub] [couchdb] nicknaychov commented on issue #2382: CouchDB backup instance - zones vs replicas?

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

nicknaychov commented on issue #2382: CouchDB backup instance - zones vs replicas?
URL: https://github.com/apache/couchdb/issues/2382#issuecomment-572965171
 
 
   I will try to combine my findings so far, hopefully would be useful to somebody else.
   
   Z parameter is no longer supported, but even if you use it CouchDB will not complain so you will end up with *fake* zoning see #2386 . Thus the link https://web.archive.org/web/20160429122538/https://cloudant.com/blog/choosing-zone-configurations-for-bigcouch is not much relevant and do not try to apply it.
   
   Use placement instead, which seems smarter and more user-friendly.
   
   CouchDB does not have R/W optimizations when you use placement (zoning), which I think should be improved, thus performance. 
   
   It seems that the *placement* implementation does not benefit of zoning at all, i.e. if you have two sites and if quorum can be satisfied only by the nodes in site A, R/W will still be sent over WAN to site B, which I think is a pure waste of resources.
   Example 2 nodes in site A and 1 node in site B,  placement = <zone-name-1>:2,<zone-name-2>:1
   
   Am I right, or I misunderstood something?
   
   Thanks

----------------------------------------------------------------
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