You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Lan Ding (Jira)" <ji...@apache.org> on 2025/03/27 02:14:00 UTC

[jira] [Commented] (KAFKA-19024) Enhance the client behaviour when it tries to exceed the `group.share.max.groups`

    [ https://issues.apache.org/jira/browse/KAFKA-19024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17938778#comment-17938778 ] 

Lan Ding commented on KAFKA-19024:
----------------------------------

Hi [~schofielaj],  If this ticket is still open, may I take it over?

> Enhance the client behaviour when it tries to exceed the `group.share.max.groups`
> ---------------------------------------------------------------------------------
>
>                 Key: KAFKA-19024
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19024
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Sanskar Jhajharia
>            Assignee: Andrew Schofield
>            Priority: Minor
>
> For share groups we use the `group.share.max.groups` config to define the number of max share groups we allow. However, when we exceed the same, the client logs do not specify any such error and simply do not consume. The group doesn't get created but the client continues to send Heartbeats hoping for one of the existing groups to shut down and allowing it to form a group. Having a log or an exception in the client logs will help them debug such situations accurately.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)