Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4497D10BBB for ; Mon, 9 Dec 2013 21:48:11 +0000 (UTC) Received: (qmail 48079 invoked by uid 500); 9 Dec 2013 21:48:10 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 48031 invoked by uid 500); 9 Dec 2013 21:48:10 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 48017 invoked by uid 99); 9 Dec 2013 21:48:10 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Dec 2013 21:48:10 +0000 Date: Mon, 9 Dec 2013 21:48:10 +0000 (UTC) From: "Dave Cottlehuber (JIRA)" To: dev@couchdb.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (COUCHDB-1946) Trying to replicate NPM grinds to a halt after 40GB MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)