[ 
https://issues.apache.org/jira/browse/YARN-10538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shilun Fan updated YARN-10538:
------------------------------
         Component/s: resourcemanager
        Hadoop Flags: Reviewed
    Target Version/s: 3.2.3, 3.3.1, 3.4.0

> Add recommissioning nodes to the list of updated nodes returned to the AM
> -------------------------------------------------------------------------
>
>                 Key: YARN-10538
>                 URL: https://issues.apache.org/jira/browse/YARN-10538
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.9.1, 3.1.1
>            Reporter: Srinivas S T
>            Assignee: Srinivas S T
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0, 3.3.1, 3.2.3
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> YARN-6483 introduced nodes that transitioned to DECOMMISSIONING state to the 
> list of updated nodes returned to the AM. This allows the Spark application 
> master to gracefully decommission its containers on the decommissioning node. 
> But if the node were to be recommissioned, the Spark application master would 
> not be aware of this. We propose to add recommissioned node to the list of 
> updated nodes sent to the AM when a recommission node transition occurs.



--
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

Reply via email to