[
https://issues.apache.org/jira/browse/YARN-8761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761465#comment-16761465
]
Eric Yang commented on YARN-8761:
---------------------------------
[~billie.rinaldi] There is a schematic change in the way container can be
decommissioned. While this schematic change is marginal, it still has
potential risk to let user stumble on hostname gaps that did not exist in
branch-3.1 and branch-3.2 before. I don't have a opinion not to back port
this, the flag is to let customer to know the change of behavior. It may be
insignificant that most users don't care.
> Service AM support for decommissioning component instances
> ----------------------------------------------------------
>
> Key: YARN-8761
> URL: https://issues.apache.org/jira/browse/YARN-8761
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Billie Rinaldi
> Assignee: Billie Rinaldi
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: YARN-8761.01.patch, YARN-8761.02.patch,
> YARN-8761.03.patch, YARN-8761.04.patch, YARN-8761.05.patch
>
>
> The idea behind this feature is to have a flex down where specific component
> instances are removed. Currently on a flex down, the service AM chooses for
> removal the component instances with the highest IDs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
