[
https://issues.apache.org/jira/browse/COUCHDB-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15546713#comment-15546713
]
Paul Joseph Davis commented on COUCHDB-3178:
--------------------------------------------
Yeap. That fixed it. Kind of amazing how something like that can have such a
profound impact on the system. For background, what would happen is that when
we got a call to the clustered _changes endpoint, we'd fire off RPC workers for
each shard and wait to hear back from them. Which we never did so we'd timeout.
However, the rpc workers were still furiously looking for docs that passed the
filter which was just wasting resources since their coordinator had already
abandoned them.
So now filtered changes feeds work again when they have to filter lots of rows
(once we merge the PR and get it into a relase).
> 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)
