[
https://issues.apache.org/jira/browse/YARN-7216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang updated YARN-7216:
----------------------------
Attachment: YARN-7216.yarn-native-services.001.patch
- Implemented SOLR as storage for Yarnfile.
- Added REST API to list configuration from SOLR.
To enable ability to store Yarnfile on SOLR, in yarn-site.xml, add the
following properties:
{code}
<property>
<name>yarn.api-service.solr.storage.enabled</name>
<value>true</value>
<description>
Flag to enable YARN Services for storing service configuration
on solr.
</description>
</property>
<property>
<name>yarn.api-service.solr.url</name>
<value>http://localhost:8983/solr/yarn</value>
<description>
URL to Solr server for storing YARN Service config.
</description>
</property>
{code}
> 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
> Attachments: YARN-7216.yarn-native-services.001.patch
>
>
> 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]/spec
> /ws/v1/services/[service_name]/status
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
