[ https://issues.apache.org/jira/browse/MAPREDUCE-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J reopened MAPREDUCE-4345: -------------------------------- Thanks Bikas! Agree it is related to resurrecting RM restart. Arun - It isn't a duplicate, at least the way I see it the MAPREDUCE-4326 targets a restart-recovery while this one I'd opened to target proper HA (multiple RMs, failing over automatically, with client code covered too). It is what may come after restart-ability is achieved. Thanks, I've reopened it :) > ZK-based High Availability (HA) for ResourceManager (RM) > -------------------------------------------------------- > > Key: MAPREDUCE-4345 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4345 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Reporter: Harsh J > Assignee: Bikas Saha > > One of the goals presented on MAPREDUCE-279 was to have high availability. > One way that was discussed, per Mahadev/others on > https://issues.apache.org/jira/browse/MAPREDUCE-2648 and other places, was ZK: > {quote} > 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. > {quote} > There is now MAPREDUCE-4343 that tracks recoverability via ZK. This JIRA is > meant to track HA via ZK. > Currently there isn't a HA solution for RM, via ZK or otherwise. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira