[ 
https://issues.apache.org/jira/browse/HADOOP-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726339#action_12726339
 ] 

Jie Qiu commented on HADOOP-6121:
---------------------------------

Good suggestion on ZK with Jobtracker. 

Do you know who is implementing ZK for the NameNode? How doese it works?  
Currently, we employed the database-like replication approach to ship log from 
primary to standby(multiple standbys).  We also plan to support different level 
synchnization, i.e. tight, loose. 

For tight mode, we guarantee primary disk write and standby disk write. For 
loose mode, we guarantee primary disk write and standby receive log.

> 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.

Reply via email to