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 "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2012/10/04 02:09:08 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=13469010#comment-13469010 ] 

Alejandro Abdelnur commented on MAPREDUCE-2648:
-----------------------------------------------

Devaraj, Abhijit,

It has been more than a year since your last comments and a patch was never uploaded. What is the status of this on your your end? 
                
> 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
>            Assignee: 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira