[
https://issues.apache.org/jira/browse/YARN-8761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16609763#comment-16609763
]
Billie Rinaldi commented on YARN-8761:
--------------------------------------
I think to allow removing specific component instances, we will need to
maintain a list of decommissioned instances in the Component spec for the
service. This will prevent future AM attempts from assigning containers to the
decommissioned instances. We should be able to support decommissioning by
component instance name or by instance hostname
(componentInstanceName.serviceName.user.domain).
> 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
>
> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
