Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <18526310.27311276194073674.JavaMail.jira@thor>
Date: Thu, 10 Jun 2010 14:21:13 -0400 (EDT)
From: "Filipe Manana (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Updated: (COUCHDB-793) replication hangs (recent @dev
 thread)
In-Reply-To: <28002940.27261276193896893.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Filipe Manana updated COUCHDB-793:
----------------------------------

    Attachment: replication-hangs.patch

> replication hangs (recent @dev thread)
> --------------------------------------
>
>                 Key: COUCHDB-793
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-793
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 0.11
>         Environment: trunk and 0.11 partially
>            Reporter: Filipe Manana
>         Attachments: replication-hangs.patch
>
>
> Following the recent @dev thread about the replication.js test hanging, the following patch fixes 2 causes for this:
> 1) In couch_rep_reader, if the reader_loop process finishes before all monitored processes (which read docs from source db) finish, the couch_db_writer process will never receive the message {complete, HighSeq}. This happens more frequently for replication by doc_ids
> 2) For trunk only, in couch_rep_writer, if we replicate a document with attachments and the first couch_rep_httpc upload (remote target db case) try doesn't succeed, subsequent tries will always fail because the couch_work_queue used was closed after the first try and the streaming function passed to ibrowse will always returns eof.
> The following patch fixes both problems. With it, running the replication test several times in a row (20+) succeeds, as well as all other JS and Etap tests.
> Reason 1) might be the cause for COUCHDB-596 as well.

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