couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filipe Manana (Commented) (JIRA)" <j...@apache.org>
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:50:51 GMT

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

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

Dirkjan I agree it's confusing. It is no longer the case in the branch 1.2.x and onwards.
Is it ok for you to close this ticket then?
                
> _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

        

Mime
View raw message