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 2018/02/01 10:25:26 UTC

[GitHub] sajeeval opened a new issue #1138: Different replication recovery scenarios

sajeeval opened a new issue #1138: Different replication recovery scenarios 
URL: https://github.com/apache/couchdb/issues/1138
 
 
   Hello,
   
   I just want to understand the difference of replication recovery mechanism (Unidirectional) for following two scenarios. 
   
   1. Replication fails due to a network failure. Master gets updated during the network outage. Once network is back after **1 hour**; 
   - Does replication resume where it left off? How it finds where it should start from? If the master was highly active and there were lot of changes, does the replication starts from the beginning or it just resumes? 
   
   2. If the network outage is 1 day
   - Does the replication resume, or restart from the scratch (copy whole database)? 
   
   3. Stop couchdb slave. Upgrade OS. Upgrade couchdb version. Start couch service
   - Does the replication resume or restart (start from the beginning) ?
   
   Actually we have couchdb instances which are significantly large in size. So it is important for us to know what happens for above scenarios. I think if the replication restarts from the scratch (without resuming ) resource utilization would be much higher; which is not preferred. 
   
   Thank you.
   Sajeeva
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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