[
https://issues.apache.org/jira/browse/YARN-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Subru Krishnan updated YARN-3671:
---------------------------------
Attachment: YARN-3671-YARN-2915-v4.patch
bq. Here, the scheduler is passed in via reference. If the RM switches to
standby and then switches back to active, the scheduler object will be
re-created and the reference will be updated in RMContext, but the reference
here won't be updated, which cause the scheduler object here outdated?
Good question [~jianhe]. The scheduler object will *not* be outdated as
{{FederationStateStoreService}} is an active service and the
{{FederationStateStoreHeartbeat}} is initialized on it's _serviceStart_:
{code}
stateStoreHeartbeat = new FederationStateStoreHeartbeat(subClusterId,
stateStoreClient, rmContext.getScheduler());
{code}
To double-check, I have updated the {{TestFederationRMStateStoreService}} with
an explicit transtion to standby and then back to active.
I have also renamed "state-store.heartbeat-interval" -->
"state-store.heartbeat-interval-secs" in v4 of the patch as you suggested.
> 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,
> YARN-3671-YARN-2915-v2.patch, YARN-3671-YARN-2915-v3.patch,
> YARN-3671-YARN-2915-v4.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]
