ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhe (Joe) Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-15519) Add Service Wizard with nodes in the maintenance mode
Date Wed, 20 Apr 2016 17:11:25 GMT

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

Zhe (Joe) Wang updated AMBARI-15519:
------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed to trunk 8c6796f38bb9be8f4b9f88dce35861ad4ce653d3

> 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
>
>         Attachments: AMBARI-15519.v0.patch
>
>
> 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)

Mime
View raw message