[GitHub] [couchdb] nicknaychov edited a comment on issue #2386: CouchDB Zones: How to verify if zones are setup correctly?

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

nicknaychov edited a comment on issue #2386: CouchDB Zones: How to verify if zones are setup correctly?
URL: https://github.com/apache/couchdb/issues/2386#issuecomment-572687087
 
 
   @kocolosk wow this is big. You just saved me a lot of time and I believe to many other people as well! 
   
   I think that should be put somewhere in important place of the documentation:
   
   **r,w and z parameters are not supported anymore.** 
   (Even better if couchdb display error if sees them, would be awesome. )
   
   **n parameter will be overridden by "placement" if present** - I saw this already in the docs. 
   
   I think CouchDB is great project but there is a lot of pitfalls and lack of good docs, which makes a lot of people to give up and move on with other solutions. 
   
   I think replication, n (replicas) and placement are maybe overlapping and confusing concepts for some, thus clarification when and what should be used will help many people I am sure.
   
   Example, in my case I have a lot of DBs which get added and removed on the fly by the upper layer logic, so I think I need special script for detecting that and start/stop DB replications. 
   So replication is not suitable in my case. 
   
   If I use the approach with n=3 replicas, 2 nodes on local site and one on remote site, that means unnecessary WAN load and delayed performance. 
   
   Thus I think optimal solution would be using DB placement with two replicas hosted on local site and 1 on remote. This way I think will achieve that R/W will occur only on the local site(if both nodes are up) to avoid unnecessary WAN delays, while in case of emergency I will have backup.
   
   If @kocolosk or somebody else can confirm my statements will be much appreciated.
   I think that would be good example and candidate for the best practices section - deployments.
   Thank you.
     

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