Github user davisp commented on the issue:
https://github.com/apache/couchdb-couch/pull/236
@nickva I don't think its worth having two settings when we're looking at
minutes as anything under load ends up reverting to the current behavior
(assuming we don't introduce bugs ;).
Ah, hrm. I guess if nothing has an open changes listener and we're just
issuing reads against it that could happen. Though I'm not sure how much of an
issue that really is. But assuming we want to change as little as possible
that'd be best to avoid. I wouldn't change is_idle directly since that changes
how it interacts with max_dbs_open. However adding a check in couch_server to
check against the last read activity might be useful. I'll have to think on
that more cause it either means tracking more state or adding message passing
and given that couch_server and couch_db_updater's are two of the busiest
gen_servers already that'd be mmmmbad.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
