[
https://issues.apache.org/jira/browse/HADOOP-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726370#action_12726370
]
Jie Qiu commented on HADOOP-6121:
---------------------------------
Currently, in my experiment, my approach follows:
1. Hook Hadoop for Memory write and Disk write.
Memory write means changes to the BTree, the corresponding log operations
(OP_ADD, OP_RENAME, OP_DELETE,....)
Disk write means write the log to disks
2. Replication log from primary node to slaves(one standy at this stage)
3. Replay log in slaves
4. Standby heartbeat primary and take over if it feels primary down
I would like to know other approaches for Hadoop HA on NameNode. What's
additional requirements on Hadoop HA?
> 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.