Closed jcguion closed 2 years ago
ping @ppatierno @cescoffier
It's the bug @tsegismont chased, and yes I confirm that the problem was fixed in the Apache Kafka client. Note that 2.7 is also available.
Would be great to uptake at least 2.7 as it contains some features we'd love to leverage. Any plans for that?
we actually have a planned upgrade to 3.0.0 when Vert.x 4.3.0 is released
Questions
We observed high CPU usage from an idle Kafka consumer and isolated the issue to a known problem that has been fixed in the Apache Kafka client (KAFKA-10254 & KAFKA-10134) and made available as version 2.6.1 (current Vert.x Kafka dependency is on 2.6.0).
Version
3.9.3, although current 3.9.6 SNAPSHOT has the same 2.6.0 dependency.
Context
Consumer connects to Kafka broker and shows CPU burn.
Suggestion
An uptake of the patched Apache Kafka client (2.6.1).