You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/23 22:28:39 UTC
[jira] [Resolved] (MAPREDUCE-802) Simplify the job updated event
notification between Jobtracker and schedulers
[ https://issues.apache.org/jira/browse/MAPREDUCE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved MAPREDUCE-802.
----------------------------------------
Resolution: Fixed
Stale for all intents and purposes.
> Simplify the job updated event notification between Jobtracker and schedulers
> -----------------------------------------------------------------------------
>
> Key: MAPREDUCE-802
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-802
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobtracker
> Reporter: Hemanth Yamijala
> Assignee: Sreekanth Ramakrishnan
> Attachments: eventmodel-1.patch, eventmodel-2.patch, eventmodel-3.patch
>
>
> HADOOP-4053 and HADOOP-4149 added events to take care of updates to the state / property of a job like the run state / priority of a job notified to the scheduler. We've seen some issues with this framework, such as the following:
> - Events are not raised correctly at all places. If a new code path is added to kill a job, raising events is missed out.
> - Events are raised with incorrect event data. For e.g. typically start time value is missed out.
> The resulting contract break between jobtracker and schedulers has lead to problems in the capacity scheduler where jobs remain stuck in the queue without being ever removed and so on.
> It has proven complicated to get this right in the framework and fixes have typically still left dangling cases. Or new code paths introduce new bugs.
> This JIRA is about trying to simplify the interaction model so that it is more robust and works well.
--
This message was sent by Atlassian JIRA
(v6.2#6252)