[ https://issues.apache.org/jira/browse/AMBARI-24577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599148#comment-16599148 ]
Hudson commented on AMBARI-24577: --------------------------------- SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #212 (See [https://builds.apache.org/job/Ambari-branch-2.7/212/]) [AMBARI-24577] Services should display the Stop button if any of their (ishanbhatt.1989: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=be87ee58c3bbd4f315d65836dc5d996211ba3463]) * (edit) ambari-web/app/controllers/main/service/item.js * (edit) ambari-web/test/controllers/main/service/item_test.js > Services should display the "Stop" button if any of their components are > started > -------------------------------------------------------------------------------- > > Key: AMBARI-24577 > URL: https://issues.apache.org/jira/browse/AMBARI-24577 > Project: Ambari > Issue Type: Bug > Components: ambari-web > Reporter: Ishan Bhatt > Assignee: Ishan Bhatt > Priority: Major > Labels: pull-request-available > Fix For: trunk > > Time Spent: 1h 20m > Remaining Estimate: 0h > > In Ambari 2.7, the "Stop" button for each service is only available if all > its components are started. This means that if any component is not started > (or down), the rest of the components must be stopped individually from every > host. > [!5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/162070/162070_5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png] > > For services where one component cannot be started (for example, due to > memory limitations), stopping the service can be a very painful exercise. > Please enable the "stop" button to be triggered, if any component of a > service can be stopped. > Similarly for the Start button -- This message was sent by Atlassian JIRA (v7.6.3#76005)