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

Posted to yarn-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/23 22:52:40 UTC

[jira] [Moved] (YARN-2344) Provide a mechanism to pause the jobtracker

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

Allen Wittenauer moved MAPREDUCE-828 to YARN-2344:
--------------------------------------------------

    Component/s:     (was: jobtracker)
                 resourcemanager
            Key: YARN-2344  (was: MAPREDUCE-828)
        Project: Hadoop YARN  (was: Hadoop Map/Reduce)

> Provide a mechanism to pause the jobtracker
> -------------------------------------------
>
>                 Key: YARN-2344
>                 URL: https://issues.apache.org/jira/browse/YARN-2344
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: resourcemanager
>            Reporter: Hemanth Yamijala
>
> We've seen scenarios when we have needed to stop the namenode for a maintenance activity. In such scenarios, if the jobtracker (JT) continues to run, jobs would fail due to initialization or task failures (due to DFS). We could restart the JT enabling job recovery, during such scenarios. But restart has proved to be a very intrusive activity, particularly if the JT is not at fault itself and does not require a restart. The ask is for a admin-controlled feature to pause the JT which would take it to a state somewhat analogous to the safe mode of DFS.



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