[HADOOP-9593] stack trace printed at ERROR for all yarn clients without hadoop.home set

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha1
• Fix Version/s: 2.1.0-beta
• Component/s: util
• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 23/May/13 17:16
• Updated: 12/May/16 18:23
• Resolved: 24/May/13 19:58

Description

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

Issue Links

• is duplicated by: HADOOP-9546 "setsid exited with exit code" message on each hadoop command
• relates to: HADOOP-9482 regression: unable to create a file in the file:/// filesystem unless HADOOP_HOME_DIR or hadoop.home.dir is set
• relates to: HADOOP-9422 HADOOP_HOME should not be required to be set to be able to launch commands using hadoop.util.Shell