[ https://issues.apache.org/jira/browse/AMBARI-21508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ishan Bhatt updated AMBARI-21508: --------------------------------- Fix Version/s: trunk > Lifecycle: Start,Start All Visibility > ------------------------------------- > > Key: AMBARI-21508 > URL: https://issues.apache.org/jira/browse/AMBARI-21508 > Project: Ambari > Issue Type: New Feature > Components: ambari-web > Affects Versions: 3.0.0 > Reporter: Ishan Bhatt > Assignee: Ishan Bhatt > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-21508.patch > > > Today Start, or Start All buttons for an individual service are greyed out if > all masters are started. The issue is if you have a lot of workers that are > not started, you still want to start/start all to get them started. We should > change the behavior so it's more like this: > Any component Stopped -> "Start/Start All" is available > All components Started -> "Start/Start All" is not available > All components (that are not in maintenance mode or on hosts in maintenance > mode) are Started -> "Start/Start All" is not available > That way if any component is stopped we can start it with a Start/Start All. > The behavior should be that Ambari looks at all components for the service > and if any are in the stopped state, it will start those components. > Maintenance mode should be respected and if a component or host is in > maintenance mode, they will be ignored from this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)