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
Describe the bug
GMS is producing errors, when rolled out with limited access rights. In our case, we only allowed GMS to use groups with a specific prefix.
I found that GMS is not aware of those custom groups, even when they are set in the global kafka properties.
Describe the bug
GMS is producing errors, when rolled out with limited access rights. In our case, we only allowed GMS to use groups with a specific prefix.
I found that GMS is not aware of those custom groups, even when they are set in the global kafka properties.
Reason being is here: https://github.com/acryldata/datahub-helm/blob/master/charts/datahub/subcharts/datahub-gms/templates/deployment.yaml#L299
We do use standalone consumers and we want to use custom groups at the same time.
Workaround
Added these consumer group names to the ENV manually.
Log extract
2025-02-11 11:36:26,065 [pool-6-thread-1] ERROR c.d.m.d.throttle.KafkaThrottleSensor:252 - Error fetching consumer group offsets.
Caused by: org.apache.kafka.common.errors.GroupAuthorizationException: Group authorization failed.
The text was updated successfully, but these errors were encountered: