You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/10/21 17:56:00 UTC
[jira] [Commented] (YARN-11360) Add number of decommissioning nodes to YARN cluster metrics.
[ https://issues.apache.org/jira/browse/YARN-11360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17622389#comment-17622389 ]
ASF GitHub Bot commented on YARN-11360:
---------------------------------------
cnauroth opened a new pull request, #5060:
URL: https://github.com/apache/hadoop/pull/5060
### Description of PR
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.
### How was this patch tested?
The patch adds new unit tests for the ResourceManager RPC, correct merging of the metric through the router service and `yarn top`.
### For code changes:
- [X] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
- [X] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
- [X] 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)?
- [X] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, `NOTICE-binary` files?
> Add number of decommissioning 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
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Priority: Major
>
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org