You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by nickva <gi...@git.apache.org> on 2016/08/01 18:11:05 UTC
[GitHub] couchdb issue #425: Improve reduce function overlow handling
Github user nickva commented on the issue:
https://github.com/apache/couchdb/pull/425
@kxepal
The problem is the setting is really a tri-state switch of "disabled", "warning", "enabled". SELinux setup on RHEL works the same (disabled, permissive, where it logs but don't block access, and enabled where it blocks access)
Something like `reduce_limit_debug = true | false` needs an explanation how it interacts with `reduce_limit`. For example reduce `reduce_limit_debug` would only work with `reduce_limit = false`, which is not intuitive. When `reduce_limit = true` there is not much need to log as it already blows up and user will find out.
@rnewson Any thoughts on this?
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---