You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Brian Swan (JIRA)" <ji...@apache.org> on 2013/06/17 21:19:20 UTC
[jira] [Created] (AMBARI-2406) Clarify how service state is
determined, make STATE optional
Brian Swan created AMBARI-2406:
----------------------------------
Summary: Clarify how service state is determined, make STATE optional
Key: AMBARI-2406
URL: https://issues.apache.org/jira/browse/AMBARI-2406
Project: Ambari
Issue Type: Improvement
Reporter: Brian Swan
Priority: Minor
How Ambari determines service state (https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/service-resources.md) is not clear. For example, is HDFS considered STARTED when the NameNode and all DataNodes are up? For alternative implementations of Ambari server, understanding how this is currently done would be helpful. Until then, making the state retuned by clusters/<cluster_name>/services/<service_name> optional would give other implementers more flexibility.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira