Github user davisp commented on the issue:
https://github.com/apache/couchdb-couch/pull/236
@nickva @eiri Aha! Different conversation!
Removing the max_dbs_open hard limit and swapping to a soft limit has been
suggested a few times and then we'd end up relying on the nfile kernel
parameter to enforce the maximum number of open databases.
The original motivation (as I recall) for adding max_dbs_open [1] was for
testing situations where people would continually hit emfile errors during runs
of the test suite. This was way back (apparently, almost nine years ago) when
we were still running the test suite out of Futon in the browser (heh). In
tradition of the early days there's no associated ticket with the explicit
reasoning and the change is part of a much huger change for other unrelated
things so the actual motivation may be lost to the sands of time.
I'd be all for removing the max limit and relying on a soft limit and idle
closures. Though before we go that route we'll want to add similar soft limits
to secondary indexes as well since we subtly rely on max_dbs_open to limit the
number of open indexes. And we'd want to call out setting the nfile parameter
higher (though I think I remember seeing this in the docs recently).
[1]
https://github.com/apache/couchdb/commit/88ec14c220592c8c0db7869c9961423e9ee97e7c
---
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.
---
