You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "Joan Touzet (JIRA)" <ji...@apache.org> on 2017/05/09 20:14:05 UTC
[jira] [Closed] (COUCHDB-1946) Trying to replicate NPM grinds to a
halt after 40GB
[ https://issues.apache.org/jira/browse/COUCHDB-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joan Touzet closed COUCHDB-1946.
--------------------------------
Resolution: Fixed
Assignee: Joan Touzet
Fix Version/s: 2.1.0
1.6.2
1.7.0
After years of inactivity I've decided to merge [~kocolosk]'s patch. This will increase CPU utilisation when writing attachments but should drastically reduce memory requirements on the target couch when replicating large attachments. If further memory reduction is required use of -erl ERL_FULLSWEEP_AFTER 0 in the launch command is recommended.
> 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
> Assignee: Joan Touzet
> Priority: Critical
> Fix For: 1.7.0, 1.6.2, 2.1.0
>
> 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.3.15#6346)