nerdvegas opened a new issue #1399: backoff after replication failure should be configurable URL: https://github.com/apache/couchdb/issues/1399 I have multiple remote clusters connected via bidirectional replication jobs. Sometimes there are extended outages preventing one cluster from seeing another, and I would like replication to start working again in short order once the outage is resolved. However, it seems I can't set the backoff factor, and replication can take a long time to retry. If I manually restart my nodes, everything works, ie replication starts working again. It seems that I just need this to be configurable - I would like crashing replication jobs to retry at least once per 5 minutes. ## Expected Behavior See above - crashing replication jobs should retry after a max configurable delay, rather than exponentially backing off with no control over the backoff params. ## Current Behavior No control over how long it takes for a crashing replication job to retry. ## Context This is a problem for me currently, I have to work around it by implementing my own systemd timer which checks for crashing replication jobs every 5 mins and restarts the couch node in order to force replication retry. ## Your Environment Couchdb v2.1.0, Cent 7.
---------------------------------------------------------------- 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
