couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kocoloski (JIRA)" <>
Subject [jira] Commented: (COUCHDB-365) Replication hangs and won't restart
Date Fri, 29 May 2009 05:40:45 GMT


Adam Kocoloski commented on COUCHDB-365:

Thanks, Antony.  The second problem you encountered is due to the use of list_to_existing_atom/1.
 I replaced it with plain-old list_to_atom.

Instead of recalculating the "MeAndMyLinks" list every time, I added some guards to memory_footprint
so that it doesn't try to call process_info with a dead Pid.  Hopefully this resolves the

> Replication hangs and won't restart
> -----------------------------------
>                 Key: COUCHDB-365
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 0.9.1
>         Environment: Replicate to Ubuntu from OSX, both running R13B
>            Reporter: Antony Blakey
> Partway through a replication I get this:
>   {"error":"json_encode","reason":"{bad_term,{couch_rep,'-memory_footprint/1-fun-0-',2}}"}
> as the response from the replication request. Attempting to restart replication results
>   [info] [<0.5511.0>] replication "1f78d088910dc73016c0b16b2fb84aac" already running
at <0.4203.0>
> but the replication has hung.

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

View raw message