[
https://issues.apache.org/jira/browse/MAPREDUCE-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403261#comment-13403261
]
Tom White commented on MAPREDUCE-4328:
--------------------------------------
> 3. Doesn't accept new job submissions.
To be clear - the client would get a failure, right? The current patch doesn't
do that yet as far as I can see.
A few other pieces of feedback on the patch:
* The -refreshNodes option in MRAdmin was deleted from the usage message.
* Rather than putting markup in the JobTracker (in getSafeModeText()), do the
formatting in the JSP or a utility class like JSPUtil (which already exists).
* Change JobTracker's getSafeMode() method to isInSafeMode(), to mirror
NameNode.
* MRAdmin introduced a couple of unneeded imports: DistributedFileSystem,
org.mortbay.log.Log
> Add the option to quiesce the JobTracker
> ----------------------------------------
>
> Key: MAPREDUCE-4328
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4328
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv1
> Affects Versions: 1.0.3
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
> Attachments: MAPREDUCE-4328.patch
>
>
> In several failure scenarios it would be very handy to have an option to
> quiesce the JobTracker.
> Recently, we saw a case where the NameNode had to be rebooted at a customer
> due to a random hardware failure - in such a case it would have been nice to
> not lose jobs by quiescing the JobTracker.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
