hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7216) Missing ability to list configuration vs status
Date Tue, 26 Sep 2017 20:40:00 GMT

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

Eric Yang commented on YARN-7216:

In hdfs:///user/$USER/.yarn/yarn/services/(service)/(service).json file contains the running
status of the YARN service.  Configuration is also retrieved from the same file.  In some
situations, the expansion of variables in status can prevent the object to be reused for start/stop
containers.  The proposal is to change storage of configuration to SOLR.  This can improve
the efficiency of storing small metadata on HDFS, and provide faster lookup capability for
service configuration.

The list of enhancements include:

# Create service will write configuration metadata to SOLR.
# Delete service will remove configuration metadata from SOLR.
# Lookup of service configuration will retrieve  metadata from SOLR.
# Lookup of service status will retrieve status json from HDFS (unchanged from today's behavior)

> Missing ability to list configuration vs status
> -----------------------------------------------
>                 Key: YARN-7216
>                 URL: https://issues.apache.org/jira/browse/YARN-7216
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, applications
>            Reporter: Eric Yang
>            Assignee: Eric Yang
> API Server has /ws/v1/services/{service_name}.  This REST end point returns Services
object which contains both configuration and status.  When status or macro based parameters
changed in Services object, it can confuse UI code to making configuration changes.  The suggestion
is to preserve a copy of configuration object independent of status object.  This gives UI
ability to change services configuration and update configuration.
> Similar to Ambari, it might provide better information if we have the following separated
REST end points:
> {code}
>  /ws/v1/services/[service_name]/config
>  /ws/v1/services/[service_name]/status
> {code}

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