[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[ https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13676912#comment-13676912 ] Hudson commented on HADOOP-9593: Integrated in Hadoop-Yarn-trunk #232 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/232/]) HADOOP-9593. Changing CHANGES.txt to reflect merge to branch-2.1-beta. (Revision 1490105) Result = SUCCESS acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1490105 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt stack trace printed at ERROR for all yarn clients without hadoop.home set - Key: HADOOP-9593 URL: https://issues.apache.org/jira/browse/HADOOP-9593 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0 Reporter: Steve Loughran Assignee: Steve Loughran Fix For: 3.0.0, 2.1.0-beta Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch This is the problem of HADOOP-9482 now showing up in a different application -one whose log4j settings haven't turned off all Shell logging. Unless you do that, all yarn clients will have a stack trace at error in their logs, which is generating false alarms and is utterly pointless. Why does this merit a stack trace? Why log it at error? It's not an error for a client app to not have these values set as long as they have the relevant JARs on their classpath. And if they don't, they'll get some classpath error instead -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[ https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13676990#comment-13676990 ] Hudson commented on HADOOP-9593: Integrated in Hadoop-Hdfs-trunk #1422 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1422/]) HADOOP-9593. Changing CHANGES.txt to reflect merge to branch-2.1-beta. (Revision 1490105) Result = FAILURE acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1490105 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt stack trace printed at ERROR for all yarn clients without hadoop.home set - Key: HADOOP-9593 URL: https://issues.apache.org/jira/browse/HADOOP-9593 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0 Reporter: Steve Loughran Assignee: Steve Loughran Fix For: 3.0.0, 2.1.0-beta Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch This is the problem of HADOOP-9482 now showing up in a different application -one whose log4j settings haven't turned off all Shell logging. Unless you do that, all yarn clients will have a stack trace at error in their logs, which is generating false alarms and is utterly pointless. Why does this merit a stack trace? Why log it at error? It's not an error for a client app to not have these values set as long as they have the relevant JARs on their classpath. And if they don't, they'll get some classpath error instead -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[ https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13676558#comment-13676558 ] Arun C Murthy commented on HADOOP-9593: --- Looks like this hasn't been merged to branch-2 yet, I'll do it. stack trace printed at ERROR for all yarn clients without hadoop.home set - Key: HADOOP-9593 URL: https://issues.apache.org/jira/browse/HADOOP-9593 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0 Reporter: Steve Loughran Assignee: Steve Loughran Fix For: 3.0.0, 2.1.0-beta Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch This is the problem of HADOOP-9482 now showing up in a different application -one whose log4j settings haven't turned off all Shell logging. Unless you do that, all yarn clients will have a stack trace at error in their logs, which is generating false alarms and is utterly pointless. Why does this merit a stack trace? Why log it at error? It's not an error for a client app to not have these values set as long as they have the relevant JARs on their classpath. And if they don't, they'll get some classpath error instead -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[ https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13676574#comment-13676574 ] Arun C Murthy commented on HADOOP-9593: --- Done. stack trace printed at ERROR for all yarn clients without hadoop.home set - Key: HADOOP-9593 URL: https://issues.apache.org/jira/browse/HADOOP-9593 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0 Reporter: Steve Loughran Assignee: Steve Loughran Fix For: 3.0.0, 2.1.0-beta Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch This is the problem of HADOOP-9482 now showing up in a different application -one whose log4j settings haven't turned off all Shell logging. Unless you do that, all yarn clients will have a stack trace at error in their logs, which is generating false alarms and is utterly pointless. Why does this merit a stack trace? Why log it at error? It's not an error for a client app to not have these values set as long as they have the relevant JARs on their classpath. And if they don't, they'll get some classpath error instead -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[ https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13676586#comment-13676586 ] Hudson commented on HADOOP-9593: Integrated in Hadoop-trunk-Commit #3868 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/3868/]) HADOOP-9593. Changing CHANGES.txt to reflect merge to branch-2.1-beta. (Revision 1490105) Result = SUCCESS acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1490105 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt stack trace printed at ERROR for all yarn clients without hadoop.home set - Key: HADOOP-9593 URL: https://issues.apache.org/jira/browse/HADOOP-9593 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0 Reporter: Steve Loughran Assignee: Steve Loughran Fix For: 3.0.0, 2.1.0-beta Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch This is the problem of HADOOP-9482 now showing up in a different application -one whose log4j settings haven't turned off all Shell logging. Unless you do that, all yarn clients will have a stack trace at error in their logs, which is generating false alarms and is utterly pointless. Why does this merit a stack trace? Why log it at error? It's not an error for a client app to not have these values set as long as they have the relevant JARs on their classpath. And if they don't, they'll get some classpath error instead -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[ https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666199#comment-13666199 ] Hudson commented on HADOOP-9593: Integrated in Hadoop-Yarn-trunk #219 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/219/]) HADOOP-9593 stack trace printed at ERROR for all yarn clients without hadoop.home set (Revision 1485842) Result = SUCCESS stevel : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1485842 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Shell.java stack trace printed at ERROR for all yarn clients without hadoop.home set - Key: HADOOP-9593 URL: https://issues.apache.org/jira/browse/HADOOP-9593 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0 Reporter: Steve Loughran Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch This is the problem of HADOOP-9482 now showing up in a different application -one whose log4j settings haven't turned off all Shell logging. Unless you do that, all yarn clients will have a stack trace at error in their logs, which is generating false alarms and is utterly pointless. Why does this merit a stack trace? Why log it at error? It's not an error for a client app to not have these values set as long as they have the relevant JARs on their classpath. And if they don't, they'll get some classpath error instead -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[ https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666287#comment-13666287 ] Hudson commented on HADOOP-9593: Integrated in Hadoop-Hdfs-trunk #1409 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1409/]) HADOOP-9593 stack trace printed at ERROR for all yarn clients without hadoop.home set (Revision 1485842) Result = FAILURE stevel : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1485842 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Shell.java stack trace printed at ERROR for all yarn clients without hadoop.home set - Key: HADOOP-9593 URL: https://issues.apache.org/jira/browse/HADOOP-9593 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0 Reporter: Steve Loughran Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch This is the problem of HADOOP-9482 now showing up in a different application -one whose log4j settings haven't turned off all Shell logging. Unless you do that, all yarn clients will have a stack trace at error in their logs, which is generating false alarms and is utterly pointless. Why does this merit a stack trace? Why log it at error? It's not an error for a client app to not have these values set as long as they have the relevant JARs on their classpath. And if they don't, they'll get some classpath error instead -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[ https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666334#comment-13666334 ] Hudson commented on HADOOP-9593: Integrated in Hadoop-Mapreduce-trunk #1435 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1435/]) HADOOP-9593 stack trace printed at ERROR for all yarn clients without hadoop.home set (Revision 1485842) Result = SUCCESS stevel : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1485842 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Shell.java stack trace printed at ERROR for all yarn clients without hadoop.home set - Key: HADOOP-9593 URL: https://issues.apache.org/jira/browse/HADOOP-9593 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0 Reporter: Steve Loughran Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch This is the problem of HADOOP-9482 now showing up in a different application -one whose log4j settings haven't turned off all Shell logging. Unless you do that, all yarn clients will have a stack trace at error in their logs, which is generating false alarms and is utterly pointless. Why does this merit a stack trace? Why log it at error? It's not an error for a client app to not have these values set as long as they have the relevant JARs on their classpath. And if they don't, they'll get some classpath error instead -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[
https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13665372#comment-13665372
]
Steve Loughran commented on HADOOP-9593:
stack
{code}
013-05-23 17:58:09,766 [main] ERROR util.Shell
(Shell.java:checkHadoopHome(230)) - Failed to detect a valid hadoop home
directory
java.io.IOException: HADOOP_HOME or hadoop.home.dir are not set.
at org.apache.hadoop.util.Shell.checkHadoopHome(Shell.java:213)
at org.apache.hadoop.util.Shell.clinit(Shell.java:236)
at org.apache.hadoop.util.PlatformName.clinit(PlatformName.java:35)
at
org.apache.hadoop.security.UserGroupInformation.getOSLoginModuleName(UserGroupInformation.java:314)
at
org.apache.hadoop.security.UserGroupInformation.clinit(UserGroupInformation.java:359)
at org.apache.hadoop.ipc.RPC.getProtocolProxy(RPC.java:450)
at org.apache.hadoop.ipc.RPC.getProtocolProxy(RPC.java:604)
at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:561)
at
org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl.init(ClientRMProtocolPBClientImpl.java:104)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.apache.hadoop.yarn.factories.impl.pb.RpcClientFactoryPBImpl.getClient(RpcClientFactoryPBImpl.java:73)
at
org.apache.hadoop.yarn.ipc.HadoopYarnProtoRPC.getProxy(HadoopYarnProtoRPC.java:46)
{code}
Also I get some gratuitous complaints that setsuid didn't get used but still
failed
{code}
2013-05-23 17:58:09,778 [main] WARN util.Shell
(Shell.java:isSetsidSupported(308)) - setsid is not available on this machine.
So not using it.
2013-05-23 17:58:09,778 [main] INFO util.Shell
(Shell.java:isSetsidSupported(311)) - setsid exited with exit code
{code}
stack trace printed at ERROR for all yarn clients without hadoop.home set
-
Key: HADOOP-9593
URL: https://issues.apache.org/jira/browse/HADOOP-9593
Project: Hadoop Common
Issue Type: Bug
Components: util
Reporter: Steve Loughran
This is the problem of HADOOP-9482 now showing up in a different application
-one whose log4j settings haven't turned off all Shell logging.
Unless you do that, all yarn clients will have a stack trace at error in
their logs, which is generating false alarms and is utterly pointless. Why
does this merit a stack trace? Why log it at error? It's not an error for a
client app to not have these values set as long as they have the relevant
JARs on their classpath. And if they don't, they'll get some classpath error
instead
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[ https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13665389#comment-13665389 ] Chris Nauroth commented on HADOOP-9593: --- Hi, Steve. Is this the same as HADOOP-9422? (Thanks for adding that it impacts YARN clients too though.) stack trace printed at ERROR for all yarn clients without hadoop.home set - Key: HADOOP-9593 URL: https://issues.apache.org/jira/browse/HADOOP-9593 Project: Hadoop Common Issue Type: Bug Components: util Reporter: Steve Loughran This is the problem of HADOOP-9482 now showing up in a different application -one whose log4j settings haven't turned off all Shell logging. Unless you do that, all yarn clients will have a stack trace at error in their logs, which is generating false alarms and is utterly pointless. Why does this merit a stack trace? Why log it at error? It's not an error for a client app to not have these values set as long as they have the relevant JARs on their classpath. And if they don't, they'll get some classpath error instead -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[ https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13665457#comment-13665457 ] Jason Lowe commented on HADOOP-9593: The annoying setsid message is also tracked by HADOOP-9546. stack trace printed at ERROR for all yarn clients without hadoop.home set - Key: HADOOP-9593 URL: https://issues.apache.org/jira/browse/HADOOP-9593 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0 Reporter: Steve Loughran Attachments: HADOOP-9593-001.patch This is the problem of HADOOP-9482 now showing up in a different application -one whose log4j settings haven't turned off all Shell logging. Unless you do that, all yarn clients will have a stack trace at error in their logs, which is generating false alarms and is utterly pointless. Why does this merit a stack trace? Why log it at error? It's not an error for a client app to not have these values set as long as they have the relevant JARs on their classpath. And if they don't, they'll get some classpath error instead -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[
https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13665460#comment-13665460
]
Chris Nauroth commented on HADOOP-9593:
---
+1 for the patch. Thanks, Steve. Downgrading to debug level sounds like a
helpful first step.
{code}
+LOG.debug(setsid exited with exit code
+ + (shexec != null ? shexec.getExitCode() : (null
executor));
{code}
Really minor nitpick: did you intend to have a closing paren inside the string
literal for (null executor ?
stack trace printed at ERROR for all yarn clients without hadoop.home set
-
Key: HADOOP-9593
URL: https://issues.apache.org/jira/browse/HADOOP-9593
Project: Hadoop Common
Issue Type: Bug
Components: util
Affects Versions: 3.0.0
Reporter: Steve Loughran
Attachments: HADOOP-9593-001.patch
This is the problem of HADOOP-9482 now showing up in a different application
-one whose log4j settings haven't turned off all Shell logging.
Unless you do that, all yarn clients will have a stack trace at error in
their logs, which is generating false alarms and is utterly pointless. Why
does this merit a stack trace? Why log it at error? It's not an error for a
client app to not have these values set as long as they have the relevant
JARs on their classpath. And if they don't, they'll get some classpath error
instead
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[
https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13665503#comment-13665503
]
Hadoop QA commented on HADOOP-9593:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12584539/HADOOP-9593-001.patch
against trunk revision .
{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}. The javadoc tool did not generate any
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 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2560//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2560//console
This message is automatically generated.
stack trace printed at ERROR for all yarn clients without hadoop.home set
-
Key: HADOOP-9593
URL: https://issues.apache.org/jira/browse/HADOOP-9593
Project: Hadoop Common
Issue Type: Bug
Components: util
Affects Versions: 3.0.0
Reporter: Steve Loughran
Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch
This is the problem of HADOOP-9482 now showing up in a different application
-one whose log4j settings haven't turned off all Shell logging.
Unless you do that, all yarn clients will have a stack trace at error in
their logs, which is generating false alarms and is utterly pointless. Why
does this merit a stack trace? Why log it at error? It's not an error for a
client app to not have these values set as long as they have the relevant
JARs on their classpath. And if they don't, they'll get some classpath error
instead
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[ https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13665501#comment-13665501 ] Steve Loughran commented on HADOOP-9593: Chris -you're right. new patch to follow stack trace printed at ERROR for all yarn clients without hadoop.home set - Key: HADOOP-9593 URL: https://issues.apache.org/jira/browse/HADOOP-9593 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0 Reporter: Steve Loughran Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch This is the problem of HADOOP-9482 now showing up in a different application -one whose log4j settings haven't turned off all Shell logging. Unless you do that, all yarn clients will have a stack trace at error in their logs, which is generating false alarms and is utterly pointless. Why does this merit a stack trace? Why log it at error? It's not an error for a client app to not have these values set as long as they have the relevant JARs on their classpath. And if they don't, they'll get some classpath error instead -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[
https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13665548#comment-13665548
]
Hadoop QA commented on HADOOP-9593:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12584556/HADOOP-9593-002.patch
against trunk revision .
{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}. The javadoc tool did not generate any
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 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2561//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2561//console
This message is automatically generated.
stack trace printed at ERROR for all yarn clients without hadoop.home set
-
Key: HADOOP-9593
URL: https://issues.apache.org/jira/browse/HADOOP-9593
Project: Hadoop Common
Issue Type: Bug
Components: util
Affects Versions: 3.0.0
Reporter: Steve Loughran
Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch
This is the problem of HADOOP-9482 now showing up in a different application
-one whose log4j settings haven't turned off all Shell logging.
Unless you do that, all yarn clients will have a stack trace at error in
their logs, which is generating false alarms and is utterly pointless. Why
does this merit a stack trace? Why log it at error? It's not an error for a
client app to not have these values set as long as they have the relevant
JARs on their classpath. And if they don't, they'll get some classpath error
instead
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[ https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13665602#comment-13665602 ] Steve Loughran commented on HADOOP-9593: OK, applied to trunk; it wouldn't take on branch-2. Should I create a new JIRA for that? stack trace printed at ERROR for all yarn clients without hadoop.home set - Key: HADOOP-9593 URL: https://issues.apache.org/jira/browse/HADOOP-9593 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0 Reporter: Steve Loughran Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch This is the problem of HADOOP-9482 now showing up in a different application -one whose log4j settings haven't turned off all Shell logging. Unless you do that, all yarn clients will have a stack trace at error in their logs, which is generating false alarms and is utterly pointless. Why does this merit a stack trace? Why log it at error? It's not an error for a client app to not have these values set as long as they have the relevant JARs on their classpath. And if they don't, they'll get some classpath error instead -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[ https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13665607#comment-13665607 ] Hudson commented on HADOOP-9593: Integrated in Hadoop-trunk-Commit #3783 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/3783/]) HADOOP-9593 stack trace printed at ERROR for all yarn clients without hadoop.home set (Revision 1485842) Result = SUCCESS stevel : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1485842 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Shell.java stack trace printed at ERROR for all yarn clients without hadoop.home set - Key: HADOOP-9593 URL: https://issues.apache.org/jira/browse/HADOOP-9593 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0 Reporter: Steve Loughran Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch This is the problem of HADOOP-9482 now showing up in a different application -one whose log4j settings haven't turned off all Shell logging. Unless you do that, all yarn clients will have a stack trace at error in their logs, which is generating false alarms and is utterly pointless. Why does this merit a stack trace? Why log it at error? It's not an error for a client app to not have these values set as long as they have the relevant JARs on their classpath. And if they don't, they'll get some classpath error instead -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[
https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13665609#comment-13665609
]
Chris Nauroth commented on HADOOP-9593:
---
{quote}
OK, applied to trunk; it wouldn't take on branch-2. Should I create a new JIRA
for that?
{quote}
I'd say it's not necessary. We're pretty close to merging HADOOP-8562 from
trunk to branch-2, and I expect your trunk patch will apply cleanly after that.
stack trace printed at ERROR for all yarn clients without hadoop.home set
-
Key: HADOOP-9593
URL: https://issues.apache.org/jira/browse/HADOOP-9593
Project: Hadoop Common
Issue Type: Bug
Components: util
Affects Versions: 3.0.0
Reporter: Steve Loughran
Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch
This is the problem of HADOOP-9482 now showing up in a different application
-one whose log4j settings haven't turned off all Shell logging.
Unless you do that, all yarn clients will have a stack trace at error in
their logs, which is generating false alarms and is utterly pointless. Why
does this merit a stack trace? Why log it at error? It's not an error for a
client app to not have these values set as long as they have the relevant
JARs on their classpath. And if they don't, they'll get some classpath error
instead
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-9593) stack trace printed at ERROR for all yarn clients without hadoop.home set
[ https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13665852#comment-13665852 ] Arpit Agarwal commented on HADOOP-9593: --- HADOOP-8562 has been merged into branch-2. stack trace printed at ERROR for all yarn clients without hadoop.home set - Key: HADOOP-9593 URL: https://issues.apache.org/jira/browse/HADOOP-9593 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 3.0.0 Reporter: Steve Loughran Attachments: HADOOP-9593-001.patch, HADOOP-9593-002.patch This is the problem of HADOOP-9482 now showing up in a different application -one whose log4j settings haven't turned off all Shell logging. Unless you do that, all yarn clients will have a stack trace at error in their logs, which is generating false alarms and is utterly pointless. Why does this merit a stack trace? Why log it at error? It's not an error for a client app to not have these values set as long as they have the relevant JARs on their classpath. And if they don't, they'll get some classpath error instead -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
