[
https://issues.apache.org/jira/browse/MAPREDUCE-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439751#comment-13439751
]
Eli Collins commented on MAPREDUCE-4328:
----------------------------------------
Hey Arun,
Per ATM's above comment shouldn't we do the analogous feature for trunk first?
Seems like this would be YARN safemode since the AM really isn't equivalent to
the JT for this feature.
Also, please motivate this feature by outlining the primary use cases. I don't
think you need to write a design doc but a basic paragraph or two would be
good. From my experience admins would like to quiesce the JT so they can
prevent new jobs from being launched while draining the queue of current jobs
to facilitate a cluster upgrade.
Thanks,
Eli
> 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
> Fix For: 1.2.0
>
> Attachments: MAPREDUCE-4328.patch, MAPREDUCE-4328.patch,
> TestJobTrackerQuiescence.java
>
>
> 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
