Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 06-29-2017 02:00 PM
I have installed 3-node Kafka cluster as a part of HDP 2.5.3. At some point, we have tried to remove some of configuration groups and re-create them. Right now, we have remnants of previous groups (two deleted configuration groups). One of those deleted groups has node in it (03) which is duplicated (exists in Deleted and Kafka-...-03 groups). I tried to remove one of those appearances but I could not.
Is there any way to remove old configuration groups and duplicated node?
Thanks!
Created 06-29-2017 02:05 PM
After deleting you will see the config group name as "Deleted" in the ambari UI that is an issue reported as part of : https://issues.apache.org/jira/browse/AMBARI-20435
.
In order to clean the Deleted config group completely you will need to find the config_group id and then you can run the following SQL queries then restart "ambari-server"
delete from ambari."serviceconfighosts" where service_config_id in (select service_config_id from serviceconfig where group_id=<REPLACE>); delete from ambari."serviceconfigmapping" where service_config_id in (select service_config_id from serviceconfig where group_id=<REPLACE>); delete from ambari.serviceconfig where group_id=<REPLACE>;
.
**NOTE:** Please collect the Ambari DB Dump before modifying the DB manually.
Replace the <REPLACE> value with the config_group id which you want to cleanup.
.
Created 06-29-2017 02:05 PM
After deleting you will see the config group name as "Deleted" in the ambari UI that is an issue reported as part of : https://issues.apache.org/jira/browse/AMBARI-20435
.
In order to clean the Deleted config group completely you will need to find the config_group id and then you can run the following SQL queries then restart "ambari-server"
delete from ambari."serviceconfighosts" where service_config_id in (select service_config_id from serviceconfig where group_id=<REPLACE>); delete from ambari."serviceconfigmapping" where service_config_id in (select service_config_id from serviceconfig where group_id=<REPLACE>); delete from ambari.serviceconfig where group_id=<REPLACE>;
.
**NOTE:** Please collect the Ambari DB Dump before modifying the DB manually.
Replace the <REPLACE> value with the config_group id which you want to cleanup.
.
Created 06-29-2017 08:52 PM
Thanks a lot! It worked.