You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/09/10 18:03:33 UTC
[jira] [Commented] (AMBARI-7237) No start action for stopped
service in MM mode Stack 1.3
[ https://issues.apache.org/jira/browse/AMBARI-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128646#comment-14128646 ]
Hudson commented on AMBARI-7237:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #200 (See [https://builds.apache.org/job/Ambari-trunk-Commit/200/])
AMBARI-7237. No start action for stopped service in MM mode Stack 1.3 (dlysnichenko) (dlysnichenko: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dcc00b69b3350729123cbf43dd80cf0da314bae6)
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ServiceResourceProvider.java
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ServiceResourceProviderTest.java
> 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 the 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 best component state (e.g. INSTALLED -> STARTED)
> # now the best 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 started, entire service will be showed as started.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)