[
https://issues.apache.org/jira/browse/COUCHDB-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274305#comment-15274305
]
ASF subversion and git services commented on COUCHDB-3006:
----------------------------------------------------------
Commit 13326bb4b265c09c37f8088c6432f80f495ef0cd in couchdb-couch-replicator's
branch refs/heads/master from [~kzx]
[
https://git-wip-us.apache.org/repos/asf?p=couchdb-couch-replicator.git;h=13326bb
]
Add jittered delay during replication error handling
For one-to-many replications, when source fails, it can create a stampede
effect. A jittered delay is used to avoid that. Delay is random, in a range
proportional to current number of replications, with a maximum of 1 minute.
Seed random number generator within each replication process with a
non-deterministic value, otherwise the same sequence of delays is generated
for all replications.
Jira: COUCHDB-3006
> Source failure in one source to many target replications causes a stampede
> --------------------------------------------------------------------------
>
> Key: COUCHDB-3006
> URL: https://issues.apache.org/jira/browse/COUCHDB-3006
> Project: CouchDB
> Issue Type: Bug
> Reporter: Nick Vatamaniuc
>
> For multiple replications from a single source to multiple targets. If source
> fails, all replications post an error state back their replication document
> and attempt to restart. This creates a stampede effect and causes sharp load
> spikes on the replication cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)