hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-737) High Availability support for Hadoop
Date Fri, 08 Feb 2013 17:07:15 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574626#comment-13574626

Harsh J commented on MAPREDUCE-737:

Hey Jie,

Are you still working on any JT HA bits? If not, can we close this out in favor of the other
related JIRAs (as the talk is duplicated)? HDFS-1623 covers the NN HA part btw.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message