[
https://issues.apache.org/jira/browse/ACCUMULO-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs resolved ACCUMULO-2304.
-----------------------------------------
Resolution: Not A Problem
Fix Version/s: (was: 2.0.0)
I don't think it's a problem to routinely run production at DEBUG level, if it
is routine to want to troubleshoot a production system. If we bump everything
up to INFO, then it doesn't change what is logged or the value of the log
messages... it just crams things into a smaller range of log levels, which
reduces the granularity at which users can configure their logging. So, I don't
think this should be done.
If this is still an issue, please consider opening a new issue at
https://github.com/apache/accumulo/issues
> Change Log Levels to not necessitate running DEBUG in production
> ----------------------------------------------------------------
>
> Key: ACCUMULO-2304
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2304
> Project: Accumulo
> Issue Type: Improvement
> Components: master, tserver
> Reporter: Mike Drob
> Priority: Major
>
> Every production cluster I've seen runs logging at DEBUG in production
> because the INFO+ level messages are not very good. We should move some of
> the DEBUGs up to INFO so that it is feasible to turn DEBUG off. At least to
> the point where we no longer need to ship example configurations that leave
> it on.
> Alternatively, we could address the issues that people need DEBUG logging
> turned on for, and address the problem that way.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
