[
https://issues.apache.org/jira/browse/COUCHDB-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885119#comment-13885119
]
ASF subversion and git services commented on COUCHDB-1874:
----------------------------------------------------------
Commit b35884580436824adc7f250d9adbe857440026d7 in branch
refs/heads/1986-fix-ibrowse-infinite-async-timeout from [~dch]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=b358845 ]
ibrowse: fix async hang due to infinite timeout
- import upstream timeout fix[1]
- addresses COUCHDB-1986 and quite possibly COUCHDB-1874 as well
[1]: https://github.com/cmullaparthi/ibrowse/pull/91.patch
> 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.5#6160)
