ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gonzalo Herreros (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18358) Deleting a service with node specific configuration makes Ambari unstable
Date Mon, 12 Sep 2016 09:46:20 GMT

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

Gonzalo Herreros updated AMBARI-18358:
--------------------------------------
    Description: 
Always reproduced.

On any service, change some setting to be node specific (instead of global to the cluster).

To do so create a config group, switch to it and change some setting to be specific for that
group.

Now, stop and delete the service. The configuration is deleted but the group configuration
is left behind.

>From this moment the log will be full of " Config inconsistency exists: unknown configType=dbks-site"
(in my case the service I reproduced it was Ranger KMS).
Any attempt to add a service will get a 500.

The only workaround is going to the DB and manually delete the group configuration.

  was:
Always reproduced.

On any service change some setting to be node specific (instead of global to the cluster).
To do so create a config group, switch to it and change some setting to be specific for that
group.

Now, stop and delete the service. The configuration is deleted but the group configuration
is left behind.

>From this moment the log will be full of " Config inconsistency exists: unknown configType=dbks-site"
(in my case the service I reproduced it was Ranger KMS).
Any attempt to add a service will get a 500.

The only workaround is going to the DB and manually delete the group configuration.


> Deleting a service with node specific configuration makes Ambari unstable
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-18358
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18358
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-admin
>    Affects Versions: 2.4.0
>            Reporter: Gonzalo Herreros
>
> Always reproduced.
> On any service, change some setting to be node specific (instead of global to the cluster).

> To do so create a config group, switch to it and change some setting to be specific for
that group.
> Now, stop and delete the service. The configuration is deleted but the group configuration
is left behind.
> From this moment the log will be full of " Config inconsistency exists: unknown configType=dbks-site"
(in my case the service I reproduced it was Ranger KMS).
> Any attempt to add a service will get a 500.
> The only workaround is going to the DB and manually delete the group configuration.



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

Mime
View raw message