From common-issues-return-69395-apmail-hadoop-common-issues-archive=hadoop.apache.org@hadoop.apache.org Tue Sep 16 00:25:34 2014 Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B819C11787 for ; Tue, 16 Sep 2014 00:25:34 +0000 (UTC) Received: (qmail 16629 invoked by uid 500); 16 Sep 2014 00:25:34 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 16574 invoked by uid 500); 16 Sep 2014 00:25:34 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 16562 invoked by uid 99); 16 Sep 2014 00:25:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2014 00:25:34 +0000 Date: Tue, 16 Sep 2014 00:25:34 +0000 (UTC) From: "Hadoop QA (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-7984) Add hadoop command verbose and debug options MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-7984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134743#comment-14134743 ] 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/12668904/HADOOP-7984.patch against trunk revision 8008f0e. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 core tests{color}. The patch failed these unit tests in hadoop-common-project/hadoop-common: org.apache.hadoop.crypto.random.TestOsSecureRandom {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/4734//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/4734//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: 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)