[
https://issues.apache.org/jira/browse/COUCHDB-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837885#comment-15837885
]
ASF subversion and git services commented on COUCHDB-3277:
----------------------------------------------------------
Commit be0060f3fffc308b7532e6b99355f0e0cdede88e in couchdb-couch-replicator's
branch refs/heads/master from [~vatamane]
[
https://git-wip-us.apache.org/repos/asf?p=couchdb-couch-replicator.git;h=be0060f
]
Fix shards db name typo from previous commit
Previous commit which switched to using mem3 for replicator shard
discovery introduced a typo.
`config:get("mem3", "shard_db", "dbs")`
should be:
`config:get("mem3", "shards_db", "_dbs")`
COUCHDB-3277
> Replication manager when it finds _replicator db shards which are not part of
> a mem3 db
> ---------------------------------------------------------------------------------------
>
> Key: COUCHDB-3277
> URL: https://issues.apache.org/jira/browse/COUCHDB-3277
> Project: CouchDB
> Issue Type: Bug
> Reporter: Nick Vatamaniuc
>
> Currently replication manager scans the file system for shards which have a
> {{_replicator}} suffix when it starts up and discovers all replicator dbs.
> However, in the case if there is a {{_replicator}} shard without a
> corresponding mem3 dbs db entry, replicator manager crashes.
> These "orphan" replicator shards could be created during db creation, as
> shards are created first then an entry in the {{dbs}} db is added. Or if
> there is a move or backup process which might leave some db shards around.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
