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 "Zac Zhou (JIRA)" <ji...@apache.org> on 2019/08/05 11:18:00 UTC
[jira] [Updated] (YARN-9721) An easy method to exclude a
nodemanager from the yarn cluster cleanly
[ https://issues.apache.org/jira/browse/YARN-9721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zac Zhou updated YARN-9721:
---------------------------
Description:
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 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.
was:
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.
> 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
> Priority: Major
> 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 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-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org