You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Haibo Chen (JIRA)" <ji...@apache.org> on 2017/09/15 20:24:00 UTC
[jira] [Updated] (HADOOP-14871) Hadoop RunJar needs more debug
logs.
[ https://issues.apache.org/jira/browse/HADOOP-14871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Haibo Chen updated HADOOP-14871:
--------------------------------
Description:
Hadoop RunJar does not have much logging. In one case, one user had specified MAIN class in the jar and also provided the main class as one of the following arguments.
The extra argument to specify the main class was passed to the main class as an argument, which caused confusing exceptions. It'd be nice to have some debug logging
so that users can be warned.
In another case, we could have some logging for the client classloader as well.
> Hadoop RunJar needs more debug logs.
> ------------------------------------
>
> Key: HADOOP-14871
> URL: https://issues.apache.org/jira/browse/HADOOP-14871
> Project: Hadoop Common
> Issue Type: Wish
> Reporter: Haibo Chen
> Priority: Minor
> Labels: newbie++
>
> Hadoop RunJar does not have much logging. In one case, one user had specified MAIN class in the jar and also provided the main class as one of the following arguments.
> The extra argument to specify the main class was passed to the main class as an argument, which caused confusing exceptions. It'd be nice to have some debug logging
> so that users can be warned.
> In another case, we could have some logging for the client classloader as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org