couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dirkjan Ochtman (Commented) (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1335) _replicator document (1.1.1 to 1.1.1 continuous) lingers in Starting state
Date Mon, 07 Nov 2011 14:26:51 GMT


Dirkjan Ochtman commented on COUCHDB-1335:

You're right... the daemon that filled the source for that database wasn't running.

Still, it seems like the task shouldn't stay at "Starting"?
> _replicator document (1.1.1 to 1.1.1 continuous) lingers in Starting state
> --------------------------------------------------------------------------
>                 Key: COUCHDB-1335
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 1.1.1
>         Environment: Linux, Erlang 13B04.
>            Reporter: Dirkjan Ochtman
>             Fix For: 1.1.2
> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message