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 "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/23 22:05:41 UTC

[jira] [Resolved] (MAPREDUCE-786) Jobtracker history should be written aysnchronously to the filesystem

     [ https://issues.apache.org/jira/browse/MAPREDUCE-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved MAPREDUCE-786.
----------------------------------------

    Resolution: Incomplete

Closing this as stale, given how history is handled these days in YARN+MR.

> Jobtracker history should be written aysnchronously to the filesystem
> ---------------------------------------------------------------------
>
>                 Key: MAPREDUCE-786
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-786
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobtracker
>            Reporter: Sharad Agarwal
>            Assignee: Sharad Agarwal
>
> Jobtracker lock is held while writing the history events. This makes the jobtracker slow on flushes, especially when history is written to HDFS. History events should be written asynchronously to avoid this problem.



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