[
https://issues.apache.org/jira/browse/COUCHDB-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372695#comment-15372695
]
ASF GitHub Bot commented on COUCHDB-3054:
-----------------------------------------
GitHub user rnewson opened a pull request:
https://github.com/apache/couchdb-chttpd/pull/131
Don't end changes feed listener on heartbeat
There's no need to end and restart the changes feed listener on every
heartbeat, so don't do that.
COUCHDB-3054
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloudant/couchdb-chttpd
3054-invalidate-promptly
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-chttpd/pull/131.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #131
----
commit fc7287a9eddca2f1d114853bc555b07c0a6ea3f8
Author: Robert Newson <[email protected]>
Date: 2016-07-12T09:21:24Z
Don't end changes feed listener on heartbeat
There's no need to end and restart the changes feed listener on every
heartbeat, so don't do that.
COUCHDB-3054
----
> chttpd cache invalidation is slow
> ---------------------------------
>
> Key: COUCHDB-3054
> URL: https://issues.apache.org/jira/browse/COUCHDB-3054
> Project: CouchDB
> Issue Type: Bug
> Reporter: Robert Newson
>
> The chttpd_auth_cache module follows the changes feed of the clustered _users
> database in order to invalidate the cache whenever a document changes.
> This can take over a minute to occur. It turns out we kill the changes feed
> process when we receive a heartbeat and restart the feed, leading to a long
> delay.
> We do want to stop periodically in order to close databases that might have
> been compacted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
