[
https://issues.apache.org/jira/browse/COUCHDB-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13872345#comment-13872345
]
Nathan Caza commented on COUCHDB-1946:
--------------------------------------
I should probably mention, this is on 1.5.0
Upon further investigation, I found there are far larger documents, for
instance:
cordova@258-f88ea93535011521e52219071ebba13b
with attachments the request is 2336256011 bytes, or 2.18GiB.
Depending on how these get pushed in, I imagine a few packages like that (the
next largest is ~1.6GiB, 1.3GiB, etc..) being replicated in parallel would
explain the large memory usage, and may be the cause of this issue. And could
also explain why 12G of ram seemed to handle it.
> 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.5#6160)
