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 "Mahadev konar (JIRA)" <ji...@apache.org> on 2011/07/06 18:23:16 UTC

[jira] [Commented] (MAPREDUCE-2648) High Availability for JobTracker

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

Mahadev konar commented on MAPREDUCE-2648:
------------------------------------------

devaraj,
 Am not sure, if you already know about the MR-279 branch (the next version of MR framework). We've been trying to integrate ZK into the framework from the beginning. As for now, we are just doing restart with ZK but soon we should have a HA soln with ZK.

> High Availability for JobTracker
> --------------------------------
>
>                 Key: MAPREDUCE-2648
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2648
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>            Reporter: Devaraj K
>         Attachments: High Availability for JobTracker.pdf
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> In Hadoop cluster, JobTracker is responsible for managing the life cycle of MapReduce jobs. If JobTracker fails, then MapReduce service will not be available until JobTracker is restarted. We propose an automatic failover solution for JobTracker to address such single point of failure. It is based on Leader Election Framework suggested in ZOOKEEPER-1080
> Please refer to attached document.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira