You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Xi Wang (JIRA)" <ji...@apache.org> on 2014/11/09 04:49:33 UTC
[jira] [Updated] (AMBARI-8234) Hosts bulk options: remove state
filter on start/stop all components
[ https://issues.apache.org/jira/browse/AMBARI-8234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xi Wang updated AMBARI-8234:
----------------------------
Description:
Issue: Host list -> selected hosts -> start all components is refusing to work - says nothing to do.
*Reason*: start all components will filter all host components with 'desired state=INSTALLED' which should be "actual state=INSTALLED", so sometimes the filtered host components are empty, but in fact there are components need to start.
*Solution*: take out this HostRoles/state filtering and issue Start on all the host components for the selected hosts regardless of the actual state.
The server should just ignore Start command on host components whose actual state is STARTED.
was:
Issue: Host list -> selected hosts-> start all components is refusing to work - says nothing to do.
*Reason*: start all components will filter all host components with 'desired state=INSTALLED' which should be "actual state=INSTALLED", so sometimes the filtered host components are empty, but in fact there are components need to start.
*Solution*: take out this HostRoles/state filtering and issue Start on all the host components for the selected hosts regardless of the actual state.
The server should just ignore Start command on host components whose actual state is STARTED.
> Hosts bulk options: remove state filter on start/stop all components
> --------------------------------------------------------------------
>
> Key: AMBARI-8234
> URL: https://issues.apache.org/jira/browse/AMBARI-8234
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Xi Wang
> Assignee: Xi Wang
> Fix For: 1.7.0
>
>
> Issue: Host list -> selected hosts -> start all components is refusing to work - says nothing to do.
> *Reason*: start all components will filter all host components with 'desired state=INSTALLED' which should be "actual state=INSTALLED", so sometimes the filtered host components are empty, but in fact there are components need to start.
> *Solution*: take out this HostRoles/state filtering and issue Start on all the host components for the selected hosts regardless of the actual state.
> The server should just ignore Start command on host components whose actual state is STARTED.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)