[
https://issues.apache.org/jira/browse/COUCHDB-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871736#comment-13871736
]
Nathan Caza commented on COUCHDB-1946:
--------------------------------------
So, I've been experiencing this, I've had a script replicating 1-by-1 (no bulk
api). I haven't had any issues, EXCEPT as replication goes on, small documents
wiz by and now towards the end, all that is left is a large number of bigger
documents.
I skipped large documents the first pass, but I presume had I not, I would have
ran out of sockets/workers as they slowly filled up with the large
transfers/documents.
Also to note that one of these, as an example, is about ~40MB (a unicode
document/package I believe) , when simply gzipped becomes ~1.3MB.
Are there plans to support gzip compression?
> 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.5#6160)
