[
https://issues.apache.org/jira/browse/COUCHDB-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745926#comment-13745926
]
Paul Hirst commented on COUCHDB-1874:
-------------------------------------
+1
I've seen exactly the same problems with continuous replication. I never tried
without continuous to see if that improved things but my symptoms seem to match
what's being described here. Decent speed to start with but then gradual slow
down to orders of magnitude slower in a small number of hours.
I ended up just restarting the database every hour until my initial replication
was complete. I wish I'd just tried without continuous.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
