[
https://issues.apache.org/jira/browse/COUCHDB-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372924#comment-15372924
]
ASF subversion and git services commented on COUCHDB-3054:
----------------------------------------------------------
Commit ebea1b8f5d49fe60f326b33dbdc06176ecfea5d1 in couchdb-fabric's branch
refs/heads/master from [~rnewson]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-fabric.git;h=ebea1b8 ]
End the listener if any shard is deleted
If a database is deleted and recreated the underlying shards have a
new name. Since we're watching the old names, we will never again see
an updated event. So, we stop this process if any watched shard is
deleted and it's someone elses job to recreate the listener for the
new shards.
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)
