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

_replicator document (1.1.1 to 1.1.1 continuous) lingers in Starting state

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Not A Problem
    • Affects Version/s: 1.1.1
    • Fix Version/s: 1.2.1
    • Component/s: Replication
    • Labels:
      None
    • Environment:

      Linux, Erlang 13B04.

      Description

      I just upgraded two of our boxes to 1.1.1. I have two replication streams (between two separate databases), both administrated via the _replicator database. However, since the upgrade one of them stays in Starting state, while the other correctly moves on to replicate and reports its status as normal.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              djc Dirkjan Ochtman
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: