[
https://issues.apache.org/jira/browse/COUCHDB-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714305#action_12714305
]
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 issue.
> Replication hangs and won't restart
> -----------------------------------
>
> Key: COUCHDB-365
> URL: https://issues.apache.org/jira/browse/COUCHDB-365
> 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 in:
> [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.
