[
https://issues.apache.org/jira/browse/COUCHDB-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210729#comment-15210729
]
ASF subversion and git services commented on COUCHDB-2975:
----------------------------------------------------------
Commit 4cb517659c235c06a39ee7eb6b4150cdfded6116 in couchdb-couch-replicator's
branch refs/heads/master from [~rnewson]
[
https://git-wip-us.apache.org/repos/asf?p=couchdb-couch-replicator.git;h=4cb5176
]
Reduce likelihood of a bad replication job taking down the job supervisor
While we can't disable max_restart_intensity, we can make it unlikely
to happen. Ordinarily, we would want this behaviour, but replication
jobs involve human input. A bad password, or malformed url, etc, can
cause repeated and fast crashing.
For now, we require ten crashes within one second before we would
bounce the job supervisor. In future, we should manage replication
jobs with greater care.
COUCHDB-2975
> Automatically restart replication jobs if they crash
> ----------------------------------------------------
>
> Key: COUCHDB-2975
> URL: https://issues.apache.org/jira/browse/COUCHDB-2975
> Project: CouchDB
> Issue Type: Improvement
> Components: Replication
> Reporter: Robert Newson
>
> We currently use the temporary restart strategy for replication jobs, which
> means if they crash they are not restarted.
> Instead, let's use the transient restart strategy, ensuring they are
> restarted on abnormal termination, while still allowing these tasks to end
> successfully on completion or cancellation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
