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 "Shilun Fan (Jira)" <ji...@apache.org> on 2024/01/28 00:55:00 UTC
[jira] [Commented] (YARN-11497) Support removal of only selective node states in untracked removal flow
[ https://issues.apache.org/jira/browse/YARN-11497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811611#comment-17811611 ]
Shilun Fan commented on YARN-11497:
-----------------------------------
[~mudit-97] Thanks for the contribution! added to yarn contributor list, welcome to hadoop!
> Support removal of only selective node states in untracked removal flow
> -----------------------------------------------------------------------
>
> Key: YARN-11497
> URL: https://issues.apache.org/jira/browse/YARN-11497
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
> Affects Versions: 3.4.0
> Reporter: Mudit Sharma
> Assignee: Mudit Sharma
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
>
> Currently inactive nodes are removed from the Yarn local memory irrespective of which state they are in. This makes the node removal process not too much configurable
> After this patch: https://issues.apache.org/jira/browse/YARN-10854
> If autoscaling is enabled, lot many nodes go into DECOMMISSIONED state but still other states like LOST, SHUTDOWN are very less and systems might want them to be still visible on UI for better tracking
> The proposal is to introduce a new config, which when set, will allow only selective node states to be removed after going into untracked state.
>
> PR: [https://github.com/apache/hadoop/pull/5681]
> Any thoughts/suggestions/feedbacks are welcome!
--
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