You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2007/12/12 13:22:44 UTC
[jira] Commented: (HADOOP-2353) [hbase] review and fix logging
levels
[ https://issues.apache.org/jira/browse/HADOOP-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550942 ]
Hudson commented on HADOOP-2353:
--------------------------------
Integrated in Hadoop-Nightly #330 (See [http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/330/])
> [hbase] review and fix logging levels
> -------------------------------------
>
> Key: HADOOP-2353
> URL: https://issues.apache.org/jira/browse/HADOOP-2353
> Project: Hadoop
> Issue Type: Improvement
> Components: contrib/hbase
> Affects Versions: 0.16.0
> Reporter: Jim Kellerman
> Priority: Minor
> Fix For: 0.16.0
>
>
> 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.