[
https://issues.apache.org/jira/browse/MAPREDUCE-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901900#comment-13901900
]
Jason Lowe commented on MAPREDUCE-5641:
---------------------------------------
bq. how about not touching the current permissions of stating and making the RM
a proxy user in HDFS. Then the files would be written as the user.
The issue is not the permissions of the proposed file the RM would write,
rather the permissions of the .jhist and job.xml files written by the job.
Those are already owner by the user and the RM isn't involved at all. The
issue with the originally proposed approach is that the JHS is not the user and
therefore cannot access the necessary files to place them in the proper
locations after the job completes (something the AM normally does).
> History for failed Application Masters should be made available to the Job
> History Server
> -----------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-5641
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5641
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: applicationmaster, jobhistoryserver
> Affects Versions: 2.2.0
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: MAPREDUCE-5641.patch
>
>
> Currently, the JHS has no information about jobs whose AMs have failed. This
> is because the History is written by the AM to the intermediate folder just
> before finishing, so when it fails for any reason, this information isn't
> copied there. However, it is not lost as its in the AM's staging directory.
> To make the History available in the JHS, all we need to do is have another
> mechanism to move the History from the staging directory to the intermediate
> directory. The AM also writes a "Summary" file before exiting normally,
> which is also unavailable when the AM fails.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
