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 "Eli Collins (Updated) (JIRA)" <ji...@apache.org> on 2012/01/19 21:56:40 UTC

[jira] [Updated] (HADOOP-7984) Add hadoop command verbose and debug options

     [ https://issues.apache.org/jira/browse/HADOOP-7984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eli Collins updated HADOOP-7984:
--------------------------------

    Description: 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?  (was: It would be helpful if bin/hadoop have 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?)
    
> Add hadoop command verbose and debug options
> --------------------------------------------
>
>                 Key: HADOOP-7984
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7984
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: scripts
>            Reporter: Eli Collins
>            Priority: Minor
>              Labels: newbie
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira