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

Konstantin Shvachko commented on HADOOP-6121:
---------------------------------------------

Jie Qiu> we need to consider how to ship log between primary/standby/slaves 

Are you aware of BackupNode introduced in HADOOP-4539?
I thought the log shipping part has been solved by that. Or did you mean 
anything else?

Jie Qiu> Memory write means changes to the BTree,

What B-tree did you mean?

Jie Qiu> Standby heartbeat primary and take over if it feels primary down

How exactly the standby will decide ("feel" in your terms) that the primary is 
down?

Also it would be really good to have a document, which gives a general overview 
and details of your design. You can refer to other jiras for examples. We used 
to have design documents for large changes like the one you are attempting here.

> 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