[
https://issues.apache.org/jira/browse/MAPREDUCE-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228016#comment-13228016
]
Arun C Murthy commented on MAPREDUCE-3837:
------------------------------------------
Apologies for the late response, I missed this.
Thanks for the clarification Mayank, Tucu & Konst. I agree it's much more
palatable without all the complexities of trying to recover jobs from
point-of-crash.
Couple of questions:
a) How does it work in a secure setting?
b) We should at least add some docs on this feature.
Makes sense?
> Hadoop 22 Job tracker is not able to recover job in case of crash and after
> that no user can submit job.
> --------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3837
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3837
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.22.0
> Reporter: Mayank Bansal
> Assignee: Mayank Bansal
> Fix For: 0.24.0, 0.22.1, 0.23.2
>
> Attachments: PATCH-HADOOP-1-MAPREDUCE-3837-1.patch,
> PATCH-HADOOP-1-MAPREDUCE-3837-2.patch, PATCH-HADOOP-1-MAPREDUCE-3837.patch,
> PATCH-MAPREDUCE-3837.patch, PATCH-TRUNK-MAPREDUCE-3837.patch
>
>
> If job tracker is crashed while running , and there were some jobs are
> running , so if job tracker's property mapreduce.jobtracker.restart.recover
> is true then it should recover the job.
> However the current behavior is as follows
> jobtracker try to restore the jobs but it can not . And after that jobtracker
> closes its handle to hdfs and nobody else can submit job.
> Thanks,
> Mayank
--
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
