[
https://issues.apache.org/jira/browse/AMBARI-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Beerbower reassigned AMBARI-4760:
-------------------------------------
Assignee: Tom Beerbower
> Client-only services transition to the STARTED state
> ----------------------------------------------------
>
> Key: AMBARI-4760
> URL: https://issues.apache.org/jira/browse/AMBARI-4760
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 1.4.3
> Reporter: Ximo Guanter
> Assignee: Tom Beerbower
>
> In Ambari 1.4.1 and previous versions, a service which only contained client
> components would never transition to the "STARTED" state and would instead be
> in the "INSTALLED" state.
> This seems to have changed in Ambari 1.4.3. Client-only services now
> transition to the "STARTED" service, and it seems that trying to transition
> them to the "INSTALLED" service generates an error code 400.
> I asked about this in the Ambari user list and Sumit was kind enough to
> provide this context about the issue:
> {quote}
> The state of the service is now calculated based on the actual states of the
> master host components that belong to the service. E.g. if a master component
> (NAMENODE for HDFS) is INSTALLED then the state of the service will be
> INSTALLED.
> What is happening in the case of client only services is that the code is
> picking up the default value which happens to be STARTED. This could instead
> be computed based on the state of all non-master components - e.g. if all are
> INSTALLED then the service state is INSTALLED. Pls. open a JIRA and we can
> discuss it over there.
> I would recommend, as part of the above JIRA, we add some unit tests covering
> client only services and state of the service wrt. the state of the client.
> -Sumit
> {quote}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
