[
https://issues.apache.org/jira/browse/COUCHDB-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839738#comment-13839738
]
Adam Kocoloski commented on COUCHDB-1946:
-----------------------------------------
Hmm, this is certainly strange. Does restarting the replication after the
crash cause it to crash again?
If you happen to have an Erlang shell on the node when it's starts leaking
memory I'd be curious to see the output of something like
lists:reverse(lists:sort([{process_info(P, [memory,initial_call,dictionary]),
P} || P <- processes()])).
> Trying to replicate NPM grinds to a halt after 40GB
> ---------------------------------------------------
>
> Key: COUCHDB-1946
> URL: https://issues.apache.org/jira/browse/COUCHDB-1946
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Reporter: Marc Trudel
> Attachments: couch.log
>
>
> I have been able to replicate the Node.js NPM database until 40G or so, then
> I get this:
> https://gist.github.com/stelcheck/7723362
> I one case I have gotten a flat-out OOM error, but I didn't take a dump of
> the log output at the time.
> CentOS6.4 with CouchDB 1.5 (also tried 1.3.1, but to no avail). Also tried to
> restart replication from scratch - twice - bot cases stalling at 40GB.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
