You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Adam Kocoloski (JIRA)" <ji...@apache.org> on 2010/12/29 17:03:47 UTC

[jira] Resolved: (COUCHDB-993) Replication is crashing when changes feed was consumed

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

Adam Kocoloski resolved COUCHDB-993.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1
                   1.0.2

Applied to trunk, 1.1.x and 1.0.x.  Sebastian, the OOME you observed with this patch applied was eventually fixed in COUCHDB-968, right?

> Replication is crashing when changes feed was consumed
> ------------------------------------------------------
>
>                 Key: COUCHDB-993
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-993
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 1.0.1, 1.0.2
>            Reporter: Sebastian Cohnen
>             Fix For: 1.0.2, 1.1
>
>         Attachments: couchdb-993.patch
>
>
> Yesterday I hit a bug, where pull replication is dying which is resulting in a {exit,{json_encode,{bad_term,<0.133.0>}}} error (CouchDB is trying to encode a PID into JSON).
> Adam and Paul had a look at this issue yesterday and they found the underlying issue: There was a missing clause catching the exit message when the changes feed was consumed and ibrowse closes the HTTP connection for that feed.
> Adam wrote a quick patch yesterday, which I'll append here too (applies cleanly to 1.0.x at time of writing).
> (Sorry for any inaccuracy, I only understood the issue partially)

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