[
https://issues.apache.org/jira/browse/MAPREDUCE-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742726#action_12742726
]
eric baldeschwieler commented on MAPREDUCE-828:
-----------------------------------------------
> Jobs submitted to the JT will be queued up. However, if the job client fails
> to write the job
> files to the DFS (the step before job submission), those jobs will be lost.
Presumably the client can detect this and fail?
What does the client do if it tries to submit a job to a paused JT?
Why would the JT not process heartbeats normally (without scheduling new
tasks)? the new state seems hackish.
> Provide a mechanism to pause the jobtracker
> -------------------------------------------
>
> Key: MAPREDUCE-828
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-828
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: jobtracker
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
