[
https://issues.apache.org/jira/browse/KAFKA-9125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16968464#comment-16968464
]
ASF GitHub Bot commented on KAFKA-9125:
---------------------------------------
viktorsomogyi commented on pull request #7657: KAFKA-9125: Use metadata cache
GroupMetadataManager and TransactionStateManager
URL: https://github.com/apache/kafka/pull/7657
Currently the GroupMetadataManager and TransactionStateManager uses
zookeeper to query the number of partitions of their respective internal topic.
Instead of this it'd be much cheaper and better to use the metadataCache as
brokers will have up-to-date information about these partitions.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> GroupMetadataManager and TransactionStateManager should use metadata cache
> instead of zkClient
> ----------------------------------------------------------------------------------------------
>
> Key: KAFKA-9125
> URL: https://issues.apache.org/jira/browse/KAFKA-9125
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Viktor Somogyi-Vass
> Assignee: Viktor Somogyi-Vass
> Priority: Major
>
> Both classes query their respective topic's partition count via the zkClient.
> This however could be queried by the broker's local metadata cache.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
