Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Tue, 31 May 2011 12:46:47 +0000 (UTC)
From: "Filipe Manana (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: 
 <1230179283.55964.1306846007487.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (COUCHDB-690) replication fail -- couchdb
 crashed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Filipe Manana commented on COUCHDB-690:
---------------------------------------

Daniele,

It is. Have you tried on more recent releases? (1.0.x)

> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira