[
https://issues.apache.org/jira/browse/YARN-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16227498#comment-16227498
]
Jian He commented on YARN-6394:
-------------------------------
- containersFailed is not incremented on Flex by user, because I feel this is
user action, considering it as failed maybe not ideal.
- containersRunning inc/dec is moved from Component to ComponentInstance
Started and Stopped transition. This is because when user flex a component,
the container maybe not yet started, so the containersRunning may be not
incremented yet, so below check is added in ComponentInstance#destroy to ensure
only dec for ComponentInstance already at STARTED or READY state
{code}
if (getState() == STARTED || getState() == READY) {
component.decRunningContainers();
}
{code}
> Support specifying YARN related params in the service REST API
> --------------------------------------------------------------
>
> Key: YARN-6394
> URL: https://issues.apache.org/jira/browse/YARN-6394
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn-native-services
> Reporter: Jian He
> Assignee: Jian He
> Attachments: YARN-6394.yarn-native-services.01.patch,
> YARN-6394.yarn-native-services.02.patch,
> YARN-6394.yarn-native-services.03.patch
>
>
> Today user can specify a lot of YARN parameters (such as
> LogAggregationContext. i.e. all the fields in ApplicationSubmissionContext)
> when submit an app. The service REST API hasn't accounted for those so far.
> We need a way to allow users to specify those configs when submitting their
> service app. Basically, we probably need a separation of
> 1) configs for AM's own needs
> 2) configs for deployed services.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
