[
https://issues.apache.org/jira/browse/YARN-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436536#comment-15436536
]
Jian He commented on YARN-3671:
-------------------------------
- we already have RM_CLUSTER_ID, any chance that this can be used for
FEDERATION_SUBCLUSTER_ID ?
- This null check is unnecessary.
{code}
federationStateStoreService = createFederationStateStoreService();
if (federationStateStoreService != null) {
{code}
- I feel the SubClusterState is a bit redundant in the request object, because
the API itself already indicates the state such as register / deregister
- why you need to call reinitialize ?
{code}
public void setStateStoreClient(FederationStateStore stateStore) {
this.stateStoreClient = stateStore;
reInitialize();
}
{code}
> Integrate Federation services with ResourceManager
> --------------------------------------------------
>
> Key: YARN-3671
> URL: https://issues.apache.org/jira/browse/YARN-3671
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager, resourcemanager
> Reporter: Subru Krishnan
> Assignee: Subru Krishnan
> Attachments: YARN-3671-YARN-2915-v1.patch
>
>
> This JIRA proposes adding the ability to turn on Federation services like
> StateStore, cluster membership heartbeat etc in the RM
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]