Use KafkaAdminClient for quota enforcement + upgrade Kafka libs to 2.6 #55
Comments
rohanag12
pushed a commit
to rohanag12/kafka-helmsman
that referenced
this issue
Sep 6, 2022
Upgrade Kafka dependencies to version 2.8.1, which is the latest release in the 2.x.x series. This release depends on Zookeeper 3.5.x, so update that dependency to the latest version as well. This upgrade allows using newer Kafka features. One such feature that has an open ticket is to enforce quotas using the admin client instead of the old zookeeper client (teslamotors#55).
shrijeet-tesla
pushed a commit
that referenced
this issue
Sep 7, 2022
Upgrade Kafka dependencies to version 2.8.1, which is the latest release in the 2.x.x series. This release depends on Zookeeper 3.5.x, so update that dependency to the latest version as well. This upgrade allows using newer Kafka features. One such feature that has an open ticket is to enforce quotas using the admin client instead of the old zookeeper client (#55). Co-authored-by: Rohan Agarwal <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the current Kafka version (2.4.1), quota enforcement was implemented through the use of a Zookeeper admin client, as using the KafkaAdminClient only support quota configuration with Kafka >= 2.6, client and server-side.
With the introduction of quota enforcement functionality in this project, we had to add in the Kafka server library (which contains the ZK admin client code), which in turn required complicating the dependency environment with various Scala libraries, and scala
bazel_rules.When we are ready to upgrade Kafka to >= 2.6, it would make sense to bring remove these Scala dependencies and go back to a light-weight
dependencies.yamlwith just Java libraries. This entails#54
#53
The text was updated successfully, but these errors were encountered: