You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Patrick de Lanauze (Commented) (JIRA)" <ji...@apache.org> on 2011/09/30 15:54:45 UTC
[jira] [Commented] (COUCHDB-690) replication fail -- couchdb
crashed
[ https://issues.apache.org/jira/browse/COUCHDB-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118066#comment-13118066 ]
Patrick de Lanauze commented on COUCHDB-690:
--------------------------------------------
:( this is a showstopper for the use of couchdb in my project..
any progress on this issue ?
> replication fail -- couchdb crashed
> -----------------------------------
>
> Key: COUCHDB-690
> URL: https://issues.apache.org/jira/browse/COUCHDB-690
> Project: CouchDB
> Issue Type: Bug
> Components: Replication
> Affects Versions: 0.10.1
> Environment: linux 2.6.30.7 - debian 5.0
> Reporter: linkfluence
> Priority: Critical
> Labels: couchdb, replication
> Attachments: couch.log
>
>
> We have a database on host A with 8.5 millions document. The size of the database is ~450GO.
> We first tried to start a continuous replication on a second host B. The replication stoped after only 1Go have been copied, and the replication never started again.
> We then copied the database file from host A on host B. When the file was copied, we started a replication from A to B, then the couchdb on host B crashed. It tooks a long time to fetch a list of IDs, then it appears in the logfile that a time out occured on host B, and immediatly after the couchdb instance on host B crashed.
--
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