You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Jonathan Eagles (JIRA)" <ji...@apache.org> on 2014/04/22 18:22:19 UTC

[jira] [Commented] (MAPREDUCE-3755) Add the equivalent of JobStatus to end of JobHistory file

    [ https://issues.apache.org/jira/browse/MAPREDUCE-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976993#comment-13976993 ] 

Jonathan Eagles commented on MAPREDUCE-3755:
--------------------------------------------

[~bikassaha], does this change still make sense with the addition of the ATS? I don't have much context for this issue, but I'm trying to cleanup some old tickets and not sure whether this ticket is still an issue we want to pursue.

> Add the equivalent of JobStatus to end of JobHistory file 
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-3755
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3755
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: jobhistoryserver, mrv2
>    Affects Versions: 0.23.0
>            Reporter: Arun C Murthy
>            Assignee: Bikas Saha
>             Fix For: 0.23.2
>
>
> In MR1 we have the notion of CompletedJobStatus store to aid fast responses to job.getStatus. We need the equivalent for MR2, an option is to add the jobStatus to the end of the JobHistory file to which the JHS can easily jump ahead to and serve the query, it should also cache this for a fair number of recently completed jobs.



--
This message was sent by Atlassian JIRA
(v6.2#6252)