[
https://issues.apache.org/jira/browse/YARN-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708636#comment-13708636
]
Bikas Saha commented on YARN-149:
---------------------------------
Thanks. I looked at the draft. Will incorporate stuff from it or use it as the
base directly. In general, its slightly mixing fail-over with HA. The way RM
restart has been envisioned, with a good implementation, downtime due to
restart should not visible to users even with what is termed as a "cold"
restart. Finally, I differ on the wrapper implementation because of 1) extra
daemon to manage because in fail-over scenarios each extra actor increases the
combinatorics 2) the wrapper functionality seems to overlap the ZKFC and RM 3)
RM will need to be changed to interact with the wrapper and the changes IMO
should not be much different than those needed for direct ZKFC interaction 4)
we will not similar to HDFS patterns and that makes the system harder to
maintain and manage. In fact, what is being called as a wrapper is something
that probably does wrap around core RM functionality but remains inside the RM.
From what I see, it will be an impl of the HAProtocol interface around the core
RM startup functionality.
> ResourceManager (RM) High-Availability (HA)
> -------------------------------------------
>
> Key: YARN-149
> URL: https://issues.apache.org/jira/browse/YARN-149
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Harsh J
> Assignee: Bikas Saha
> Attachments: rm-ha-phase1-approach-draft1.pdf, rm-ha-phase1-draft2.pdf
>
>
> This jira tracks work needed to be done to support one RM instance failing
> over to another RM instance so that we can have RM HA. Work includes leader
> election, transfer of control to leader and client re-direction to new leader.
--
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
