You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2020/01/09 08:54:49 UTC

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

nicknaychov commented on issue #2386: CouchDB Zones: How to verify if zones are setup correctly?
URL: https://github.com/apache/couchdb/issues/2386#issuecomment-572457662
 
 
   thank you for answer @kocolosk .
   
   That makes things little bit clearer. Just to add, I do not use placement but just z=2. I rely on "automatic" placement, since I need second cluster to be used as backup in case main site is down. I use couchdb prior to introducing the placement option, so I am not sure if I should use it and how exactly will fit in my case. 
   
   Would you actually recommend using of placement param in favor of z parameter?
   
   Is there any link describing when we should use placement vs the z param? Maybe one of them should be deprecated in future releases if they overlap functionality in order to avoid confusion.
   
   In my case with 4 nodes, 2 zones(z=2) and n=3 without using DB placement, if request comes to zone 1 then R/W will be done only to the 2 nodes from that zone and there will be no WAN crossing, correct?
   My purpose is to avoid WAN crossing and thus slowing down the cluster.
   
   BTW Shard map looks ok:
   `"shards": {
           "00000000-55555554": [
               "couchdb@pbx1-z1.domain.ca",
               "couchdb@pbx1-z2.domain.ca",
               "couchdb@pbx2-z2.domain.ca"
           ],
           "55555555-aaaaaaa9": [
               "couchdb@pbx1-z1.domain.ca",
               "couchdb@pbx1-z2.domain.ca",
               "couchdb@pbx2-z1.domain.ca"
           ],
           "aaaaaaaa-ffffffff": [
               "couchdb@pbx1-z2.domain.ca",
               "couchdb@pbx2-z1.domain.ca",
               "couchdb@pbx2-z2.domain.ca"
           ]
       }`
   
   Many thanks to anybody who can shed some light on this.

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