[
https://issues.apache.org/jira/browse/COUCHDB-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16041526#comment-16041526
]
ASF subversion and git services commented on COUCHDB-3323:
----------------------------------------------------------
Commit ba0c10bcf49be66b042d8f0deaf14bcfda1a49bf in couchdb's branch
refs/heads/master from [~vatamane]
[ https://gitbox.apache.org/repos/asf?p=couchdb.git;h=ba0c10bc ]
Close idle dbs
Previously idle dbs, especially sys dbs like _replicator once opened
once for scanning would stay open forever. In a large cluster with many
_replicator shards that can add up to a significant overhead, mostly in terms
of number of active processes.
Add a mechanism to close dbs which have an idle db updater. Before hibernation
was used to limit the memory pressure, however that is often not enough.
Some databases are only read periodically so their updater would time
out. To prevent that from happening keep the last read timestamp in
the couch file process dictionary. Idle check then avoid closing dbs
which have been recently read from.
(Original idea for using timeouts in gen_server replies belongs to
Paul Davis)
COUCHDB-3323
> Idle dbs cause excessive overhead
> ---------------------------------
>
> Key: COUCHDB-3323
> URL: https://issues.apache.org/jira/browse/COUCHDB-3323
> Project: CouchDB
> Issue Type: Bug
> Reporter: Nick Vatamaniuc
>
> Idle dbs, especially sys_dbs like _replicator shards once opened
> once for scanning would stay open forever. In a large cluster with many
> _replicator shards that can add up to a significant overhead, mostly in terms
> of number of active processes.
> Add a mechanism to close dbs which are idle.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
