hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-6105) Sweep all INFO level logging and aggressively drop to DEBUG, and from DEBUG to TRACE
Date Mon, 28 May 2012 21:47:23 GMT

     [ https://issues.apache.org/jira/browse/HBASE-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack updated HBASE-6105:

      Tags: noob
    Labels: noob  (was: )
> Sweep all INFO level logging and aggressively drop to DEBUG, and from DEBUG to TRACE
> ------------------------------------------------------------------------------------
>                 Key: HBASE-6105
>                 URL: https://issues.apache.org/jira/browse/HBASE-6105
>             Project: HBase
>          Issue Type: Task
>    Affects Versions: 0.96.0
>            Reporter: Andrew Purtell
>              Labels: noob
> Speaking with Arjen from Facebook ops at HBaseCon, I asked if given one single request
for improving HBase operability, what would that be. The answer was to be less verbose at
INFO log level. For example, with many regions opening, anomalous events can be difficult
to pick out among the 5-6 INFO level messages per region deployment. Where multiple INFO level
messages are printed in close succession, we should consider coalescing them. For all INFO
level messages, we should be aggressive about demoting them to DEBUG level. And, since we
are now increasing the verbosity at DEBUG level, the same considerations should be applied
there, with coalescing and demotion of really detailed/low level logging to TRACE.
> Consider making this a blocker.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message