[
https://issues.apache.org/jira/browse/YARN-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16444285#comment-16444285
]
Eric Yang commented on YARN-8161:
---------------------------------
[~gsaha] My concern is that /app/v1/services/[service]/components/[component]
entry point is overloaded with multiple operations, such as start, stop, flex.
Without explicitly call out the operation to perform, container number can be
confusing to both end users and developers what operation would be performed by
the given parameters when the service is in different states. How about we
rename "state":" to "operation"? I don't think we can rely on this entry point
being smart enough to decipher user intend since human can be quite unclear in
self expression.
> 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
