hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-58) [hbase] review and fix logging levels
Date Thu, 13 Mar 2008 19:58:24 GMT

    [ https://issues.apache.org/jira/browse/HBASE-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578470#action_12578470
] 

stack commented on HBASE-58:
----------------------------

Our INFO logging level is insufficient so we always want to run at DEBUG level (but our DEBUG
level is overwhelming).  One approach would be to promote all logging to be INFO level.  We'd
then move the obviously DEBUG back down to DEBUG level.  For instance, here's an obvious DEBUG:
Everytime a filter runs currently, it makes 4 log lines:

{code}
2008-03-13 18:16:35,972 DEBUG org.apache.hadoop.hbase.filter.WhileMatchRowFilter: this.filterAllRemaining
is now: false
2008-03-13 18:16:35,972 DEBUG org.apache.hadoop.hbase.filter.WhileMatchRowFilter: Filter on
rowKey:null.  Result = false
2008-03-13 18:18:53,610 DEBUG org.apache.hadoop.hbase.filter.WhileMatchRowFilter: Successfully
read a sub-filter of type: org.apache.hadoop.hbase.filter.StopRowFilter
2008-03-13 18:18:53,610 DEBUG org.apache.hadoop.hbase.filter.WhileMatchRowFilter: Resetting.
{code}

Maybe it should make 2 or 3 at most but it should be possible to see what a filter is up though
you should have to set DEBUG to do it.

We don't have TRACE level when we go via apache-commons.   

> [hbase] review and fix logging levels
> -------------------------------------
>
>                 Key: HBASE-58
>                 URL: https://issues.apache.org/jira/browse/HBASE-58
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: Jim Kellerman
>            Priority: Minor
>
> Currently, the only way to tell what is really going on with an HBase cluster is to enable
DEBUG level logging. Unfortunately, this also generates a lot of 'noise' messages. We need
to review log messages and see which DEBUG messages should be promoted to INFO and if any
current INFO messages should be demoted to debug.
> In addition, some messages are very verbose and don't really need to be. This should
be fixed too.
> A good starting point for review would be to look at the output from test-contrib. Although
that is not everything, it is a place to start working from.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message