[ 
https://issues.apache.org/jira/browse/COUCHDB-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837172#comment-15837172
 ] 

ASF GitHub Bot commented on COUCHDB-3277:
-----------------------------------------

GitHub user nickva opened a pull request:

    https://github.com/apache/couchdb-couch-replicator/pull/53

    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

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cloudant/couchdb-couch-replicator 
couchdb-3277-typo

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-couch-replicator/pull/53.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 #53
    
----
commit be0060f3fffc308b7532e6b99355f0e0cdede88e
Author: Nick Vatamaniuc <[email protected]>
Date:   2017-01-25T04:17:26Z

    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)

Reply via email to