[MAPREDUCE-5589] MapReduce Job setup error leaves no useful info to users (when LinuxTaskController is used)

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Do
• Affects Version/s: 1.2.1
• Fix Version/s: 1.3.0
• Component/s: mrv1

Environment

I found that a significant portion of the main() in JobLocalizer will not have its output displayed in the tasklogs.

Before fix :
Error initializing attempt_201310122204_0002_m_000002_0:
java.io.IOException: Job initialization failed (1) with output: Reading task controller config from /etc/hadoop/taskcontroller.cfg
main : command provided 0
main : user is bantony
Good mapred-local-dirs are /hadoop12/scratch,/hadoop04/scratch,/hadoop09/scratch,/hadoop03/scratch,/hadoop05/scratch,/hadoop01/scratch,/hadoop11/scratch,/hadoop10/scratch,/hadoop08/scratch,/hadoop06/scratch,/hadoop07/scratch,/hadoop02/scratch

at org.apache.hadoop.mapred.LinuxTaskController.initializeJob(LinuxTaskController.java:193)
at org.apache.hadoop.mapred.TaskTracker$4.run(TaskTracker.java:1340)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1232)
at org.apache.hadoop.mapred.TaskTracker.initializeJob(TaskTracker.java:1315)
at org.apache.hadoop.mapred.TaskTracker.localizeJob(TaskTracker.java:1230)
at org.apache.hadoop.mapred.TaskTracker$5.run(TaskTracker.java:2641)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.hadoop.util.Shell$ExitCodeException:
at org.apache.hadoop.util.Shell.runCommand(Shell.java:255)
at org.apache.hadoop.util.Shell.run(Shell.java:182)
at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:375)
at org.apache.hadoop.mapred.LinuxTaskController.initializeJob(LinuxTaskController.java:186)
... 8 more

• Assignee: Benoy Antony
• Reporter: Benoy Antony
• Created: 17/Oct/13 17:43
• Updated: 16/Oct/17 19:45
• Resolved: 16/Oct/17 19:45

Issue Links

• is related to: MAPREDUCE-4012 Hadoop Job setup error leaves no useful info to users (when LinuxTaskController is used)