[
https://issues.apache.org/jira/browse/COUCHDB-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843029#comment-13843029
]
Thor Anker Lange commented on COUCHDB-1946:
-------------------------------------------
I have been using the default replicator settings before I started trying to
adjust the batch size - which did not help. Here is the last setup I tried:
{code}
{
"_id": "npmjs_repl",
"source":"http://isaacs.iriscouch.com/registry/";,
"target":"registry",
"continuous":false,
"worker_batch_size":50,
"user_ctx": {"name":"xpaadmin", "roles":["_admin"]}
}
{code}
> 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.4#6159)
