You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Lars George (JIRA)" <ji...@apache.org> on 2009/12/03 23:42:20 UTC
[jira] Updated: (HBASE-2029) Reduce shell exception dump on console
[ https://issues.apache.org/jira/browse/HBASE-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George updated HBASE-2029:
-------------------------------
Component/s: scripts
Description:
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}
was:
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}
> 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
> Priority: Minor
> Fix For: 0.21.0
>
>
> 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.