[
https://issues.apache.org/jira/browse/HADOOP-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726843#action_12726843
]
Hemanth Yamijala commented on HADOOP-6121:
------------------------------------------
bq. We find that the JobTracker only persist the state of competed and dead
jobs in DFS, not including the state of in-process jobs.
Umm. This is not true. JobTracker persists the state of running jobs as well in
the job history files and can recover from this state upon a restart. This was
done as part of HADOOP-3245.
> High Availability support for Hadoop
> ------------------------------------
>
> Key: HADOOP-6121
> URL: https://issues.apache.org/jira/browse/HADOOP-6121
> Project: Hadoop Common
> Issue Type: New Feature
> Components: dfs, mapred
> Reporter: Jie Qiu
>
> Currently, We look at the HA of Hadoop cluster. We need to consider the
> NameNode HA as well as Jobtracker HA. For NameNode, we want to build
> primary/standy or master-slaves pattern to provide NameNode HA. Therefore, we
> need to consider how to ship log between primary/standby/slaves and how
> commit "write" operation to NameNode after the agreement among
> primary/standby/slaves on log. Whether will we use Linux HA package or
> NameNode-built-in HA package without the help of outter Linux HA package.
> After NameNode become high availability, is it necessary to provide HA for
> Jobtracker? Can Jobtracker persist the states of Jobs and tasks into HA
> NameNode? Or Jobtracker also needs the same approach from NameNode for HA
> support.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.