[
https://issues.apache.org/jira/browse/YARN-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771211#comment-13771211
]
Karthik Kambatla commented on YARN-1068:
----------------------------------------
bq. What are the pros and cons of making the new service part of the existing
RMHAService instead of creating another RPC endpoint?
Sorry Bikas, I am not sure I understand the question. Can you elaborate a bit.
Little background on the thought-process that went in:
# Should RMHAAdminService be a part of RMHAProtocolService? It can be, I just
moved it to a separate service to make the code easier to understand and
maintain. Can definitely merge it back.
# Should RMHAAdminService be a part of AdminService and use the same port
instead of listening on another? I initially thought of doing that, but
refrained for two reasons: (1) Better to have two listeners to address two
protocols - the AdminProtocol and HAAdminProtocol. (2) AdminService itself is
not an Always-On service at the moment. To move it to Always-On, we need to
make it HA-aware which could potentially take longer time.
> Add admin support for HA operations
> -----------------------------------
>
> Key: YARN-1068
> URL: https://issues.apache.org/jira/browse/YARN-1068
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Affects Versions: 2.1.0-beta
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Labels: ha
> Attachments: yarn-1068-1.patch, yarn-1068-2.patch, yarn-1068-3.patch,
> yarn-1068-4.patch, yarn-1068-prelim.patch
>
>
> Support HA admin operations to facilitate transitioning the RM to Active and
> Standby states.
--
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
