[
https://issues.apache.org/jira/browse/MAPREDUCE-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314976#comment-14314976
]
Craig Welch commented on MAPREDUCE-3973:
----------------------------------------
[~revans2] I would add that I think we should also change the
AM/JobHistoryServer relationship such that the AM attempts to upload it's
history at completion via a synchronous service call to the history server
(which will write the data into the db), with a possible fallback to file
upload for timeout/server down cases. The history server should no longer look
at an intermediate-done directory in the line of requests but would continue to
have a background thread to monitor and load from there for these failure
cases/to pick up data submitted while offline.
> [Umbrella JIRA] JobHistoryServer performance improvements in YARN+MR
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-3973
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3973
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver, mrv2
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
>
> Few parallel efforts are happening w.r.t improving/fixing issues with
> JobHistoryServer in MR over YARN. This is the umbrella ticket so we have the
> complete picture.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
