hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7984) Add hadoop command verbose and debug options
Date Wed, 24 Sep 2014 09:11:34 GMT

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

Hadoop QA commented on HADOOP-7984:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12670934/HADOOP-7984.patch
  against trunk revision ef784a2.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/4798//console

This message is automatically generated.

> 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: Akira AJISAKA
>            Priority: Minor
>              Labels: newbie
>         Attachments: HADOOP-7984.patch, 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