You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/23 20:31:43 UTC

[jira] [Resolved] (MAPREDUCE-737) High Availability support for Hadoop

     [ https://issues.apache.org/jira/browse/MAPREDUCE-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved MAPREDUCE-737.
----------------------------------------

    Resolution: Duplicate

Closing this as a dupe at this point.

> 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 was sent by Atlassian JIRA
(v6.2#6252)