[
https://issues.apache.org/jira/browse/YARN-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443747#comment-16443747
]
Gour Saha commented on YARN-8161:
---------------------------------
I still don't understand why State is required for flex. A user wants to flex
means she only cares about modifying the number of containers running. It does
not matter what state the service is actually in. The service might be not
running at all, in which case the REST API should respond appropriately. The
service might be ACCEPTED state or UPGRADING state each of which should be
handed accordingly if a flex request comes in. I also don't understand where
you are getting the state STOP from.
Most importantly, I do not like end-user facing designs to be influenced by
"how beneficial it is for developers to develop/maintain code". A product
should be designed with end-user in mind.
> ServiceState FLEX should be removed
> -----------------------------------
>
> Key: YARN-8161
> URL: https://issues.apache.org/jira/browse/YARN-8161
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn-native-services
> Affects Versions: 3.1.0
> Reporter: Gour Saha
> Priority: Major
>
> ServiceState FLEX is not required to trigger flex up/down of containers and
> should be removed
--
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
