[
https://issues.apache.org/jira/browse/COUCHDB-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15546545#comment-15546545
]
Paul Joseph Davis commented on COUCHDB-3178:
--------------------------------------------
I should note, that if you have a replication with a filter that's constantly
timing out, this is likely the cause. Also, if you have that replication as a
replicator doc, we're seeing a large amount of load on various nodes because
the couchjs process count is much higher as we're filtering a whole bunch of
docs repeatedly because replications are retried by the replication manager.
So, while it seems like a small fix it should actually have a fairly sizable
impact on cluster performance and resource usage. I'll update more once I've
learned more.
> Fabric does not send message when filtering lots of documents
> -------------------------------------------------------------
>
> Key: COUCHDB-3178
> URL: https://issues.apache.org/jira/browse/COUCHDB-3178
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Reporter: Paul Joseph Davis
>
> We managed to mess up part of the fabric merge where fabric_rpc workers that
> are running filter changes end up not sending a message for long periods of
> time if no documents are passing the filter. PR Incoming.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
