[ https://issues.apache.org/jira/browse/YARN-11360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Nauroth resolved YARN-11360. ---------------------------------- Fix Version/s: 3.4.0 3.2.5 3.3.9 Hadoop Flags: Reviewed Resolution: Fixed I have committed this to trunk, branch-3.3 and branch-3.2 (after resolving a minor merge conflict). [~mkonst], [~groot] and [~abmodi], thank you for the code reviews. > 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 > Reporter: Chris Nauroth > Assignee: Chris Nauroth > Priority: Major > Labels: pull-request-available > Fix For: 3.4.0, 3.2.5, 3.3.9 > > > 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-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org