hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7984) Add hadoop command verbose and debug options
Date Sat, 20 Sep 2014 19:07:34 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14142164#comment-14142164
] 

Allen Wittenauer commented on HADOOP-7984:
------------------------------------------

We had a discussion about this in the office today.  One suggestion was that --debug and --verbose
is really the wrong operation here.  Perhaps it would be better if it was --loglevel.  This
way, one could do, for example:

{code}
hdfs --loglevel INFO foo
hdfs --loglevel WARN blah
hdfs --loglevel DEBUG blah
{code}

etc...

Rather than tying specific values to an option, make it free form.  This also gets rid of
the 'awkwardness' of having --debug being used for both shell and java components.


> Add hadoop command verbose and debug options
> --------------------------------------------
>
>                 Key: HADOOP-7984
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7984
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: scripts
>            Reporter: Eli Collins
>            Assignee: Allen Wittenauer
>            Priority: Minor
>              Labels: newbie
>         Attachments: HADOOP-7984.patch
>
>
> It would be helpful if bin/hadoop had verbose and debug flags. Currently users need to
set an env variable or prefix the command (eg "HADOOP_ROOT_LOGGER=DEBUG,console hadoop distcp")
which isn't very user friendly. We currently log INFO by default. How about we only log ERROR
and WARN by default, then -verbose triggers INFO and -debug triggers DEBUG?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message