[
https://issues.apache.org/jira/browse/KAFKA-17745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891117#comment-17891117
]
PoAn Yang commented on KAFKA-17745:
-----------------------------------
Hi [~dajac], I go through all GroupMetadataManager APIs. These APIs only do
static validation and can be moved to GroupCoordinatorService:
* consumerGroupHeartbeat
* shareGroupHeartbeat
Is any other API I miss? If not, may I take the issue? Thank you.
> 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)
