[
https://issues.apache.org/jira/browse/YARN-8761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761343#comment-16761343
]
Billie Rinaldi commented on YARN-8761:
--------------------------------------
[~eyang] [~leftnoteasy] [~sunilg] I'm interested in backporting this patch to
branch-3.2 and branch-3.1. This patch will be useful for platforms such as
OpenWhisk that have the ability to remove specific containers when scaling down.
I'm not sure I agree that this is an incompatible change. For apps that require
the component instance numbers to be linearly increasing, users can avoid using
the decommission capability and instead can use the original flex capability
for removing containers.
> 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]
