[
https://issues.apache.org/jira/browse/YARN-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Kambatla updated YARN-1027:
-----------------------------------
Attachment: yarn-1027-1.patch
Here is a first-cut patch that builds on the two approaches outlined in Bikas'
comments. The patch takes a hybrid approach - {{HAResourceManager}} extends
{{ResourceManager}} and implements {{HAServiceProtocol}}. This way, I believe
we minimize changes to {{ResourceManager}}. If need be, we can always merge
this back into the {{ResourceManager}}.
The only change to {{ResourceManager}} is that now we differentiate between
services run by ActiveRM and those run by StandbyRM. This makes it easier to
support service redirectors without adding HA logic to every service.
Verified, in pseudo-dist mode, HAResourceManager behaves as ResourceManager
when HA is not enabled. Also, ran all hadoop-yarn-server tests locally to
ensure RM changes don't cause any regressions.
Looking forward to any comments/suggestions.
> Implement RMHAServiceProtocol
> -----------------------------
>
> Key: YARN-1027
> URL: https://issues.apache.org/jira/browse/YARN-1027
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Karthik Kambatla
> Attachments: yarn-1027-1.patch
>
>
> Implement existing HAServiceProtocol from Hadoop common. This protocol is the
> single point of interaction between the RM and HA clients/services.
--
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
