hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6405) Improve configuring services through REST API
Date Mon, 10 Apr 2017 04:07:41 GMT

    [ https://issues.apache.org/jira/browse/YARN-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962410#comment-15962410

Jian He commented on YARN-6405:

bq. I don't think we should have a config file cache for each component / ProviderRole. The
cache should be at the application level, for example in ProviderUtils. It's keyed on the
src_file, which is a file in HDFS that can be shared by all roles.
Good point. I'll change to app-level. 
bq. Instead of adding a new HADOOP_XML_TEMPLATE type, could we do if (type is HADOOP_XML and
src_file is not null)?
bq. Why switch APP_NAME to SERVICE_NAME?
Since the service-UI also differentiates service vs app, ATS also stores the type as service,
I feel it is better to call it service ? I also think we may rename the Application.java object
to Service? your opinion ?
bq.  Possibly getting YARN-6335 committed will help us find new AppState bugs.
yep, we can get YARN-6355 in first
bq. We also need to make sure strict placement for unique components will still work
Yeah, currently, the REST API defines the PlacementPolicy abstraction but not used anywhere,
it still tries to use the old 'slider' way to pass everything via a blob of config key-values.
We'll need to make AM use this Placement policy.  Also, the implementation should depend on
YARN-5468 which is more general and efficient at YARN level, rather than re-inventing the

> Improve configuring services through REST API
> ---------------------------------------------
>                 Key: YARN-6405
>                 URL: https://issues.apache.org/jira/browse/YARN-6405
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Jian He
>            Assignee: Jian He
>         Attachments: YARN-6405.yarn-native-services.01.patch, YARN-6405.yarn-native-services.02.patch,
YARN-6405.yarn-native-services.03.patch, YARN-6405.yarn-native-services.04.patch
> YARN-4793 defined various ways that user can config services through the configuration
section of the REST API.  But, some semantics are not yet supported in the back-end server
(AM).  YARN-6255 has done some work, this jira is to complete this task -  support configuring
services through REST API

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message