Zac Zhou created YARN-9721: ------------------------------ Summary: An easy method to exclude a nodemanager from the yarn cluster cleanly Key: YARN-9721 URL: https://issues.apache.org/jira/browse/YARN-9721 Project: Hadoop YARN Issue Type: Sub-task Reporter: Zac Zhou Attachments: decommission nodes.png
If we want to take offline a nodemanager server, nodes.exclude-path and "rmadmin -refreshNodes" command are used to decommission the server. But this method cannot clean up the node clearly. Nodemanager servers are still in Decommissioned Nodes as the attachment shows. [YARN-4311|https://issues.apache.org/jira/browse/YARN-4311] enable a removalTimer to clean up the untracked node. But the logic of isUntrackedNode method is to restrict. If include-path is not used, no servers can meet the criteria. Using an include file would make a potential risk in maintenance. If yarn cluster is installed on cloud, nodemanager servers are created and deleted frequently. We need a way to exclude a nodemanager from the yarn cluster cleanly. Otherwise, the map of rmContext.getInactiveRMNodes() would keep growing, which would cause a memory issue of RM. -- This message was sent by Atlassian JIRA (v7.6.14#76016) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org