hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhijit Suresh Shingate (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2648) High Availability for JobTracker
Date Thu, 07 Jul 2011 14:05:16 GMT

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

Abhijit Suresh Shingate commented on MAPREDUCE-2648:
----------------------------------------------------

To add,

We tested this solution on a 100 node cluster and 1000 Jobs, it was measured that STANDBY
JobTracker can detect the failure of ACTIVE JobTracker and becomes ACTIVE and starts serving
requests in less than 1 minute. This includes failure detection time also.

It will be useful for the organizations which are already using hadoop in production environment.

> 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

        

Mime
View raw message