mapred job -status reports bad JobFile path when network ACL prevents AM access
-------------------------------------------------------------------------------
Key: MAPREDUCE-3959
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3959
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: client, mrv2
Reporter: Jason Lowe
Priority: Minor
ClientServiceDelegate checks network ACLs, and if they prevent connecting to
the AM it uses a canned job status via {{getNotRunningJob(null, RUNNING)}}.
The resulting output for this canned job shows a bad path for the JobFile
field, as the user in the canned field is "N/A" and code doesn't check for
that. For example:
{code}
Job: job_1330640712189_0001
Job File: /tmp/hadoop-yarn/staging/N/A/.staging/job_1330640712189_0001/job.xml
Job Tracking URL : N/A
Uber job : false
Number of maps: 0
Number of reduces: 0
map() completion: 0.0
reduce() completion: 0.0
Job state: RUNNING
retired: false
reason for failure:
Counters: 0
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
