Dmitry Lysnichenko created AMBARI-7237:
------------------------------------------
Summary: No start action for stopped service in MM mode Stack 1.3
Key: AMBARI-7237
URL: https://issues.apache.org/jira/browse/AMBARI-7237
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 1.7.0
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix For: 1.7.0
On stack 1.3 stop service, then put it into MM. Try to open Service Actions
menu - start option is inactive.
Here is how service state calculation worked: if component is in MM, we don't
take it's state into account when calculating entire service state. At the
extreme case when all components of a service are in MM, we return DISABLED
state for the service.
To fix current jira, I've implemented a special handling for the case when all
service components (or entire service) are in MM as follows:
we iterate over all master & slave componens and determine the worst component
state (e.g. STARTED->INSTALLED)
now the worst state for MM component becomes a calculated state for an entire
service
That means that if all components of service are in MM and at least one
component is stopped, entire service will be showed a stopped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
