[jira] [Commented] (COUCHDB-1335) _replicator document (1.1.1 to 1.1.1 continuous) lingers in Starting state

["Filipe Manana (Commented) (JIRA)" <ji...@apache.org>]

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

Filipe Manana commented on COUCHDB-1335:
----------------------------------------

Dirkjan, if you don't use the _replicator database, does the same thing happens?
The only case I can see that happening is when the target already has all changes from the source - in that case I think the _active_tasks status is left as "Starting".
                
> _replicator document (1.1.1 to 1.1.1 continuous) lingers in Starting state
> --------------------------------------------------------------------------
>
>                 Key: COUCHDB-1335
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1335
>             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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira