[
https://issues.apache.org/jira/browse/HBASE-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785869#action_12785869
]
Lars George commented on HBASE-2029:
------------------------------------
I also suggest we change the logging levels for ZK to ERROR and do the same for
HBase. The reason is that having DEBUG now on for 0.20.2 and onwards which is
good for the daemons doing it in the shell can easily deter users from the
various details printed out.
I have changed added this to hirb.rb
{code}
# Hack to turn down zk logging so it don't spew over the shell
# log4j.logger.org.apache.zookeeper=INFO
logger = org.apache.log4j.Logger.getLogger("org.apache.zookeeper")
logger.setLevel(org.apache.log4j.Level::ERROR);
# Hack to turn down HBase logging so it don't spew over the shell
logger = org.apache.log4j.Logger.getLogger("org.apache.hadoop.hbase")
logger.setLevel(org.apache.log4j.Level::ERROR);
{code}
That now yields no spurious warnings etc.
What I could think of though is having a debug option at shell start up to set
HBase debug level for the developers and advanced user. Saves from editing the
hirb.rb - but which is still not the worst for an advanced user. Not sure if we
could have something like this
{code}
$ hbase shell -debug
{code}
Should be easy I would think to detect the flag and hand it into the
org.jruy.Main call (or simply pass it on as is and let the hirb.rb handle it.
Just suggesting.
> Reduce shell exception dump on console
> --------------------------------------
>
> Key: HBASE-2029
> URL: https://issues.apache.org/jira/browse/HBASE-2029
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: scripts
> Affects Versions: 0.20.2
> Reporter: Lars George
> Assignee: Jean-Daniel Cryans
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: HBASE-2029.patch
>
>
> As discussed on IRC and seen over and over, the shell is too verbose when it
> prints Java related exceptions. The huge stack trace on the console is often
> causing more harm then actually helping.
> {noformat}
> ...
> [11:31pm] larsgeorge:
> the only concern is to keep it in sync with new changes and also reduce its
> stacktrace
> [11:31pm] larsgeorge:
> that can be quite nasty
> [11:31pm] _dodger_:
> I've seen a prime example of that on the mailing list today
> [11:32pm] larsgeorge:
> yeah, those do repeat themselves
> [11:32pm] larsgeorge:
> also that DEBUG is on by default
> [11:33pm] larsgeorge:
> mind you, that is a good idea for the daemons
> [11:33pm] larsgeorge:
> but prolly not the shell
> [11:33pm] jdcryans:
> I was thinking
> [11:33pm] larsgeorge:
> maybe we can set ERROR logging level just for the shell when it is started?
> [11:34pm] jdcryans:
> we should stop printing the stack trace for NSRE
> [11:34pm] larsgeorge:
> there are a few others of that sort
> [11:34pm] larsgeorge:
> be it ZK reconnects etc.
> [11:35pm] jdcryans:
> yeah there's a lot of hbase-generated zk-related noise
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
