[
https://issues.apache.org/jira/browse/COUCHDB-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819646#comment-13819646
]
Nathan Vander Wilt commented on COUCHDB-1874:
---------------------------------------------
I might be seeing this with CouchDB 1.5.0 without continuous (is that likely?)
replicating a decent-sized (1.5GB) database over a consumer-grade internet
connection. My replication starts alright, gets another 25% through or so…then
the replication more or less stops, the Erlang process starts taking 150% CPU,
and it starts processing all requests veeeeery slowly.
> Continuous replication slows down over time
> -------------------------------------------
>
> Key: COUCHDB-1874
> URL: https://issues.apache.org/jira/browse/COUCHDB-1874
> Project: CouchDB
> Issue Type: Bug
> Components: Replication
> Reporter: Joan Touzet
>
> As reported on the mailing list:
> bq. > Did you specify "continuous": true in the replication spec? If you
> did, do you see the same slowdown if you omit that flag?
> bq. > This sounds rather similar to a bug we encountered in early builds of
> BigCouch, but I don't remember the history of the codebase well enough to say
> whether the bug might be latent in Apache CouchDB.
> bq. Yes, I was using "continuous": true.
> bq. You're right: When disabling "continuous", replication seems more stable
> and efficient (1200 doc/sec). Thank you !
> And, from IRC:
> bq. 12:54 <+rnewson> iirc the cause we found was an unconsumed event message
> that gradually fills the mailbox, which sounds like it ought to affect
> couchdb.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
