You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can configure custom config groups for new clusters in CDP Base but we cannot create new services with custom config groups in existing CDP Base clusters
The services templates used when creating cluster and updating cluster are different :
Behaviour when updating cluster: On new services, it will apply default config group to all hosts
Excepted behaviour: On new services, custom configuration groups should be applied
Exemple of use case: IHAC on CDH 6, upgrading to CDP 7 with this ansible collection. Their clusters have multiple configuration groups on hive for HMS, HS2, and Gateway roles. When upgrading, Hive on Tez is created as a new service with all instances with the default configuration group
The text was updated successfully, but these errors were encountered:
anisf
linked a pull request
Nov 1, 2023
that will
close
this issue
We can configure custom config groups for new clusters in CDP Base but we cannot create new services with custom config groups in existing CDP Base clusters
The services templates used when creating cluster and updating cluster are different :
Behaviour when updating cluster: On new services, it will apply default config group to all hosts
Excepted behaviour: On new services, custom configuration groups should be applied
Exemple of use case: IHAC on CDH 6, upgrading to CDP 7 with this ansible collection. Their clusters have multiple configuration groups on hive for HMS, HS2, and Gateway roles. When upgrading, Hive on Tez is created as a new service with all instances with the default configuration group
The text was updated successfully, but these errors were encountered: