ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhuohui Li (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18085) Inconsistence between hosts and components leads to empty service in web ui
Date Tue, 09 Aug 2016 16:21:22 GMT

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

Zhuohui Li updated AMBARI-18085:
--------------------------------
    Description: I use the REST api to remove some nodes from existing cluster. I do as the
doc says. First stop all the components, then remove all the components(excluding installed
clients) and finally remove the nodes. However, after doing all these things, the ambari database
went into an inconsistent state. The `hostcomponentstate` and `hostcomponentdesiredstate`
table contained deleted hosts entries which could not be found in `hosts` table. This leaded
to when joining the `hosts` table and `hostcomponentstate`, we got a null HostEntity. So my
opinion is should Ambari disable deleting node operation while there are still installed clients
on the node, or should Ambari make a guarantee that the scenario I described never happens?
 (was: I use the REST api to remove some nodes from existing cluster. I do as the doc says.
First stop all the service, then remove all the services(excluding installed clients) and
finally remove the nodes. However, after doing all these things, the ambari database went
into an inconsistent state. The `hostcomponentstate` and `hostcomponentdesiredstate` table
contained deleted hosts entries which could not be found in `hosts` table. This leaded to
when joining the `hosts` table and `hostcomponentstate`, we got a null HostEntity. So my opinion
is should Ambari disable deleting node operation while there are still installed clients on
the node, or should Ambari make a guarantee that the scenario I described never happens?)

> Inconsistence between hosts and components leads to empty service in web ui
> ---------------------------------------------------------------------------
>
>                 Key: AMBARI-18085
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18085
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>         Environment: Centos6.5, HDP-2.4.2.0-258
>            Reporter: Zhuohui Li
>            Priority: Minor
>              Labels: easyfix
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> I use the REST api to remove some nodes from existing cluster. I do as the doc says.
First stop all the components, then remove all the components(excluding installed clients)
and finally remove the nodes. However, after doing all these things, the ambari database went
into an inconsistent state. The `hostcomponentstate` and `hostcomponentdesiredstate` table
contained deleted hosts entries which could not be found in `hosts` table. This leaded to
when joining the `hosts` table and `hostcomponentstate`, we got a null HostEntity. So my opinion
is should Ambari disable deleting node operation while there are still installed clients on
the node, or should Ambari make a guarantee that the scenario I described never happens?



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

Mime
View raw message