Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <725166864.1251058439458.JavaMail.jira@brutus>
Date: Sun, 23 Aug 2009 13:13:59 -0700 (PDT)
From: "Robert Newson (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Updated: (COUCHDB-481) Continuous replication stability
 issues
In-Reply-To: <993983607.1251048119369.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/COUCHDB-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Newson updated COUCHDB-481:
----------------------------------

    Fix Version/s: 0.10


Hope it's appropriate for me to set 'fix for version' but kocolosk and jan___ are seeing this (and related) issue, so I think it should appear on the 0.10 release page.

> Continuous replication stability issues
> ---------------------------------------
>
>                 Key: COUCHDB-481
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-481
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 0.10
>            Reporter: Robert Newson
>            Priority: Blocker
>             Fix For: 0.10
>
>
> I've been trying continuous replication with a different combinations of push/pull with 2, 3 and 4 nodes. I've hit several problems and discussed them on IRC with jan___ and kocolosk.
> Firstly, the status page in Futon (and the output of _active_tasks) becomes inaccurate sometimes (and does not recover). This complicates investigation of the more serious problems.
> I configured a circle of four nodes with continuous pull replication and used 'ab' to write documents to the first one. Success is for all documents to appear at all nodes. For small batches of documents, this works. It fails, every time, with large numbers. I use batch=ok on all requests and have not successfully run a 100k run. 
> The replication task at some point in the circle eventually dumps a huge stacktrace (which kocolosk has seen and I would need to sanitize private server names from before I could post) and dies, and is not restarted. Worse, the client process injecting the documents also dies sometimes.
> I have had perfect replication runs with 2 and 3 nodes in a circle, and no successful replication runs with 4 nodes. Using a star pattern (where each node pulls or pushes to the remaining three) fails even more rapidly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.