couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kocoloski (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1946) Trying to replicate NPM grinds to a halt after 40GB
Date Fri, 06 Dec 2013 04:13:36 GMT


Adam Kocoloski commented on COUCHDB-1946:

I played with setting the {{\{fullsweep_after, 0\}}} option on {{couch_file}} and {{couch_stream}}.
 It didn't have much of an effect on {{couch_stream}} (not surprising since I was already
hibernating the server after each write, but it reduced the memory consumption of the {{couch_file}}
down to ~nothing.

The reason for the {{couch_stream}} refc binary memory consumption continues to elude me.
 I think the next step may to head up the stack towards the replicator processes.  Still,

> Trying to replicate NPM grinds to a halt after 40GB
> ---------------------------------------------------
>                 Key: COUCHDB-1946
>                 URL:
>             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:
> 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

View raw message