[
https://issues.apache.org/jira/browse/YARN-11360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan updated YARN-11360:
------------------------------
Affects Version/s: 3.3.6
3.4.0
> Add number of decommissioning/shutdown nodes to YARN cluster metrics.
> ---------------------------------------------------------------------
>
> Key: YARN-11360
> URL: https://issues.apache.org/jira/browse/YARN-11360
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: client, resourcemanager
> Affects Versions: 3.4.0, 3.3.6
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0, 3.2.5, 3.3.6
>
>
> YARN cluster metrics expose counts of NodeManagers in various states
> including active and decommissioned. However, these metrics don't expose
> NodeManagers that are currently in the process of decommissioning. This can
> look a little spooky to a consumer of these metrics. First, the node drops
> out of the active count, so it seems like a node just vanished. Then, later
> (possibly hours later with consideration of graceful decommission), it comes
> back into existence in the decommissioned count.
> This issue tracks adding the decommissioning count to the metrics
> ResourceManager RPC. This also enables exposing it in the {{yarn top}}
> output. This metric is already visible through the REST API, so there isn't
> any change required there.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
