couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Cottlehuber (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1946) Trying to replicate NPM grinds to a halt after 40GB
Date Mon, 09 Dec 2013 21:48:10 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843588#comment-13843588
] 

Dave Cottlehuber commented on COUCHDB-1946:
-------------------------------------------

I'm pretty much finished a full replication of the registry with 1.5.0, multiple pipelines
etc, filling my adsl link as much as possible, and I've not had any issues. Maximum RAM went
up to ~ 12GiB (I have plenty to spare) but no hitches, need to copy individual docs across,
nor restart replication, despite many transient network issues & apparent npm disconnects.

What's people's thoughts on this?

- is this a bug or simply we propose some tuning enhancements?
- we could clearly reduce memory consumption though as [~kocolosk] pointed out this will likely
come with a cpu hit


> 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)

Mime
View raw message