[ https://issues.apache.org/jira/browse/YARN-11497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shilun Fan updated YARN-11497: ------------------------------ Component/s: resourcemanager > 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 > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org