[
https://issues.apache.org/jira/browse/HADOOP-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
