nicknaychov commented on issue #2382: CouchDB backup instance - zones vs 
replicas?
URL: https://github.com/apache/couchdb/issues/2382#issuecomment-569491393
 
 
   @nickva thanks for the really useful thoughts and links. It looks I can not 
escape from spinning up zones. I currently have 3 nodes with n=3 i.e. each node 
have full copy of the DB. I am trying to avoid shard moving, I am 
un-experienced and I feel will broke the things, so I am thinking of creating 2 
zones, first with with 2 nodes in the main datacenter and second zone with just 
one node. All this using existing setup, without creating brand new cluster, by 
just moving one of the nodes from the main datacenter to the second one. 
   I am not sure if this will work so please comment on this. In theory I think 
it should be valid since using this approach altering of existing shard map is 
not needed.
   @rnewson The upper layer logic would create and remove DBs on the fly 
constantly and I think if I  use replication instead of zones for data sync, 
that will not work out of the box, but I will have to create custom script as 
@nickva  noted above.  Also in the link which he posted it is clearly mentioned 
that using of replication for inter-cluster sync is very bad idea - "While 
perfectly acceptable, this has a vastly reduced guarantee of data freshness, 
even using continuous replication, plus increased latency and decreased 
throughput due to the serialization of data into the JSON format required for 
replication." 
   In conclusion, beside my experiment for setting zoning without doing 
re-balancing using the 3 existing nodes with n=3, I would like also to ask you 
guys for comment on if there is a secure way data to be replicated over WAN 
using zones?
   Thanks a lot

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

Reply via email to