Uploaded image for project: 'CouchDB'
  1. CouchDB
  2. COUCHDB-3277

Replication manager when it finds _replicator db shards which are not part of a mem3 db

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • None
    • None

    Description

      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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            vatamane Nick Vatamaniuc
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: