[
https://issues.apache.org/jira/browse/KAFKA-15340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101169#comment-18101169
]
Yunseop Eom commented on KAFKA-15340:
-------------------------------------
PR opened: https://github.com/apache/kafka/pull/23051
Implemented KAFKA-15340 in RequestQuotaTest. The test now connects directly to
the KRaft controller listener, verifies request-quota propagation to the
controller, and checks response throttling plus controller request-quota
metrics for ALLOCATE_PRODUCER_IDS and UPDATE_FEATURES. ALLOCATE_PRODUCER_IDS
uses the active broker id and epoch so the test exercises the successful
controller response path.
Validation: full RequestQuotaTest passed; the focused controller test passed
repeatedly; core:checkstyleTest, core:spotbugsMain, and git diff --check
passed. The change is test-only and follows Kafka contribution rules, including
the KAFKA-15340 commit title and required footers. Status: PR open and awaiting
maintainer review; not merged.
> Test request quota for kraft controller apis
> --------------------------------------------
>
> Key: KAFKA-15340
> URL: https://issues.apache.org/jira/browse/KAFKA-15340
> Project: Kafka
> Issue Type: Improvement
> Components: kraft, unit tests
> Reporter: Deng Ziming
> Priority: Major
>
> The RequestQuotaTest only tests request quota for kraft broker apis and zk
> broker apis, we should also test kraft controller apis.
> further more, maybe there are others tests we need to complement for kraft
> controller apis(not only broker apis).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
