[
https://issues.apache.org/jira/browse/COUCHDB-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889992#comment-15889992
]
ASF GitHub Bot commented on COUCHDB-3311:
-----------------------------------------
GitHub user rnewson opened a pull request:
https://github.com/apache/couchdb-couch-replicator/pull/58
Prevent couch_replicator_manager crashing when replicator db is deleted
couch_replicator_manager can crash in a couple of spots if the replicator
db is deleted between the time the scan finds it and the resume_scan message is
processed.
This patch also reverts the jitter patch which attempted to address this
situation.
COUCHDB-3311
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloudant/couchdb-couch-replicator
83663-crashes
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-couch-replicator/pull/58.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #58
----
commit 1e413b8afa6eb156eb5293d1dc0d5726cd5063fc
Author: Robert Newson <[email protected]>
Date: 2017-03-01T11:15:55Z
Revert "Restore adding some jitter-ed sleep to shard scanning code."
This reverts commit 45d739af3fcf8b4f8e3ccca152cb3c2d781dc2fc.
commit 7a2b2b68bf4afa6d20b56a8ae51361f83981412a
Author: Robert Newson <[email protected]>
Date: 2017-03-01T11:14:02Z
fix crashes when replicator db is deleted
BugzID: 83663
----
> Restore jitter-ed sleep to replicator manager shard discovery
> -------------------------------------------------------------
>
> Key: COUCHDB-3311
> URL: https://issues.apache.org/jira/browse/COUCHDB-3311
> Project: CouchDB
> Issue Type: Bug
> Reporter: Nick Vatamaniuc
>
> Jitter-ed sleep or was dropped inadvertently when we switch to using mem3
> shards instead of scanning the file system.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
