nickva commented on issue #1720: Feature Request: make a specific replication job unstoppable by the scheduler URL: https://github.com/apache/couchdb/issues/1720#issuecomment-436812313 Another way to set this up is to make the replication a `normal` (non-continuous) replication. Normal replications have priority and unless an operator explicitly dials down `max_jobs` parameter or restarts a replication node (server). The reason for this behavior is that traditionally (before the scheduling replicator was created) a `normal` replication replicates a snapshot of the database at particular time. So say you replicate from source S to target T. Then after the replication starts, you add a document do S. That document won't appear in T if replication is `normal`. If replication is `continuous` then it will. So basically if you have a bunch of continuous replications but want to make one replication unstoppable, have your user code periodically create normal replications from source to target. Monitor when the replication finishes and re-create it. In some cases it might even be helpful to use the `_replicate` endpoint which doesn't involve creating a replication document, which is ok if you create it and monitor it programmatically.
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
