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.