[
https://issues.apache.org/jira/browse/MAPREDUCE-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley moved HADOOP-6121 to MAPREDUCE-737:
-------------------------------------------------
Component/s: (was: dfs)
(was: mapred)
Key: MAPREDUCE-737 (was: HADOOP-6121)
Project: Hadoop Map/Reduce (was: Hadoop Common)
> High Availability support for Hadoop
> ------------------------------------
>
> Key: MAPREDUCE-737
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-737
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> 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.
