| Key: |
MAPREDUCE-737
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Jie Qiu
|
| Votes: |
1
|
| Watchers: |
32
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Reference
|
|
This issue relates to:
|
|
|
HDFS-243 Namenode cluster(multi namenode working in active-active mode) to keep high availability and expansivity
|
|
|
|
|
|
|
|
| Tags: |
HA, High Availability
|
|
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.
|
|
Description
|
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. |
Show » |
| No work has yet been logged on this issue.
|
|
