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 "Dmytro Molkov (JIRA)" <ji...@apache.org> on 2009/11/20 22:13:40 UTC
[jira] Created: (MAPREDUCE-1227) Allow JobTracker to pause task
scheduling
Allow JobTracker to pause task scheduling
-----------------------------------------
Key: MAPREDUCE-1227
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1227
Project: Hadoop Map/Reduce
Issue Type: New Feature
Affects Versions: 0.22.0
Reporter: Dmytro Molkov
We want to have an ability to pause task scheduling in JobTracker.
The idea is: make job tracker still accept new jobs, but delay their running and do not schedule any new tasks from the currently running jobs.
It will help for example restarting the DFS cluster without affecting jobs: pause execution, restart the DFS, running tasks will fail, but will not be scheduled until the execution is resumed, so the job does not fail.
In general it should help fix non MR problems (DFS, network, etc.) while not failing running jobs and keep accepting new ones.
What do people think of the general idea?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MAPREDUCE-1227) Allow JobTracker to pause task
scheduling
Posted by "Dmytro Molkov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmytro Molkov resolved MAPREDUCE-1227.
--------------------------------------
Resolution: Won't Fix
Closing this one since we reached a conclusion long ago.
> Allow JobTracker to pause task scheduling
> -----------------------------------------
>
> Key: MAPREDUCE-1227
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1227
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Affects Versions: 0.22.0
> Reporter: Dmytro Molkov
>
> We want to have an ability to pause task scheduling in JobTracker.
> The idea is: make job tracker still accept new jobs, but delay their running and do not schedule any new tasks from the currently running jobs.
> It will help for example restarting the DFS cluster without affecting jobs: pause execution, restart the DFS, running tasks will fail, but will not be scheduled until the execution is resumed, so the job does not fail.
> In general it should help fix non MR problems (DFS, network, etc.) while not failing running jobs and keep accepting new ones.
> What do people think of the general idea?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.