[
https://issues.apache.org/jira/browse/ACCUMULO-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888413#comment-13888413
]
Sean Busbey commented on ACCUMULO-2304:
---------------------------------------
Can we expand this to include
* Lowering some of our levels from ERROR and WARN for things that we easily
recover from
* Adding a guide to choosing a log level to our dev docs? for example, [I am a
fan of the reasoning in this blog
post|http://nurkiewicz.blogspot.com/2010/05/clean-code-clean-logs-logging-levels.html].
> 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
> Fix For: 1.7.0
>
>
> 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
(v6.1.5#6160)
