[
https://issues.apache.org/jira/browse/YARN-11425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728735#comment-17728735
]
ASF GitHub Bot commented on YARN-11425:
---------------------------------------
slfan1989 opened a new pull request, #5712:
URL: https://github.com/apache/hadoop/pull/5712
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
YARN-11425. [Hotfix] Modify Expiration Time Unit error.
During the completion of YARN-11425, the functionality of cleaning up
expired sub-clusters was implemented in the Router. However, when performing
expiration time conversion, the unit was set incorrectly. The default unit of
the thread pool is milliseconds, and the conversion should be performed in
milliseconds.
### How was this patch tested?
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> [Federation] Router Supports SubClusterCleaner
> ----------------------------------------------
>
> Key: YARN-11425
> URL: https://issues.apache.org/jira/browse/YARN-11425
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: federation
> Affects Versions: 3.4.0
> Reporter: Shilun Fan
> Assignee: Shilun Fan
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
>
> In YARN-Federation mode, once a SubCluster is registered, the SubCluster is
> always in the RUNNING state, even if the SubCluster has no heartbeat for a
> long time.
> We will let the Router automatically check the heartbeat time of the
> SubCluster, and once the heartbeat exceeds 30mins, we will set the SubCluster
> to the SC_LOST state.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
