You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jimmy Wang (Jira)" <ji...@apache.org> on 2025/01/11 09:09:00 UTC
[jira] [Commented] (KAFKA-17745) Move static request validation from GroupMetadataManager to GroupCoordinatorService
[ https://issues.apache.org/jira/browse/KAFKA-17745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912185#comment-17912185 ]
Jimmy Wang commented on KAFKA-17745:
------------------------------------
Hi [~yangpoan] , are you working on this? I'm willing to take this one.
> Move static request validation from GroupMetadataManager to GroupCoordinatorService
> -----------------------------------------------------------------------------------
>
> Key: KAFKA-17745
> URL: https://issues.apache.org/jira/browse/KAFKA-17745
> Project: Kafka
> Issue Type: Sub-task
> Reporter: David Jacot
> Priority: Major
>
> At the moment, we validate the request in the GroupMetadataManager. It means that the validation runs within the group coordinator threads. In case of rogue requests, it would unnecessarily use resources from those threads. It would be better to do the static validation in the GroupCoordinatorService while still running in the request handler threads. I haven't looked into all the details but it seems feasible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)