You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Zhe (Joe) Wang (JIRA)" <ji...@apache.org> on 2016/04/06 20:23:25 UTC

[jira] [Updated] (AMBARI-15519) Add Service Wizard with nodes in the maintenance mode

     [ https://issues.apache.org/jira/browse/AMBARI-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhe (Joe) Wang updated AMBARI-15519:
------------------------------------
    Issue Type: Task  (was: Bug)

> Add Service Wizard with nodes in the maintenance mode
> -----------------------------------------------------
>
>                 Key: AMBARI-15519
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15519
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.4.0
>            Reporter: Zhe (Joe) Wang
>            Assignee: Zhe (Joe) Wang
>             Fix For: 2.4.0
>
>
> On the cluster where some nodes are in the maintenance mode Add Service Wizard doesn't track this.
> So, user may select host in the maintenance mode to install some master component. And this component won't be installed (only record in the DB will be created for it).
> Another situation:
> there is some cluster where all nodes are in the maintenance mode. In this case ASW is almost useless. Because all new components won't be installed while it works.
> Maybe ASW should track hosts in the maintenance mode and warn user about adding components on them (Steps "Assign Masters", "Assign Slaves and Clients")? Or just don't allow to do this?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)