Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Wed, 23 Jul 2014 20:05:41 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12431118.1248254741454.31725.1406145941170@arcas>
In-Reply-To: <JIRA.12431118.1248254741454@arcas>
References: <JIRA.12431118.1248254741454@arcas>
Subject: [jira] [Resolved] (MAPREDUCE-786) Jobtracker history should be
 written aysnchronously to the filesystem
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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)