AndrewJSchofield commented on PR #19313: URL: https://github.com/apache/kafka/pull/19313#issuecomment-2809353794
@DL1231 Thank you for your patience. As discussed, the original idea of `group.share.max.groups` doesn't really work because it cannot be easily applied at the level of the cluster. While we could calculate it per broker or per GC shard, that gives quite a bad result because the point at which the limit is applied depends on hashing of group IDs, which is going to be unpredictable to the user. Since none of the other group types have a maximum number of groups, I am going to remove `group.share.max.groups` from the KIP. Sorry for the confusion, but I did not realise at the time the KIP was written that this would be problematic. https://issues.apache.org/jira/browse/KAFKA-19156 will be used to remove it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
