[
https://issues.apache.org/jira/browse/KAFKA-19024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17939146#comment-17939146
]
Andrew Schofield commented on KAFKA-19024:
------------------------------------------
There are two cases to consider for reaching the maximum capacity of groups.
1) The number of members in the group reaches the limit. I think the
`GROUP_MAX_SIZE_REACHED` error code should be used for this one. The default
error message could be improved since it says "The consumer group has reached
its max size." and, now that Kafka has multiple different group types, maybe
"The group has reached its maximum size." would be better.
2) The number of share groups reaches the limit of `group.share.max.groups`. I
don't believe that there's a maximum number of consumer groups, which seems
like an omission, so I don't think there's a separate error code at this point.
I wonder whether you could try using `GROUP_MAX_SIZE_REACHED` with an error
message that says "The maximum number of share groups has been reached."
What do you think?
> 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: Lan Ding
> 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)
