Hi Vic,
Yes, JDK 8 is still supported in kafka 3.x.x.
It'll become unsupported after kafka 4.0.0.
Thanks.
Luke
On Tue, May 23, 2023 at 9:56 AM Vic Xu wrote:
> Hi Greg
>
> I know JDK 8 will solve the problem certainly, but I wondering if JDK8 has
> been deprecated after Kafka 3? Can I use JDK
Hi Greg
I know JDK 8 will solve the problem certainly, but I wondering if JDK8 has been
deprecated after Kafka 3? Can I use JDK 8 with Kafka 3.2.1? Thank you.
On 2023/05/22 20:55:01 Greg Harris wrote:
> Vic,
>
> While you can certainly try that, I don't know if that will solve the problem.
>
Vic,
While you can certainly try that, I don't know if that will solve the problem.
The reason why JDK11 appears relevant in this context is that a class
was removed between JDK8 and JDK11. I don't know if a replacement
stack inspector with better performance was added to JDK17 and used
within
Hi Greg,
I found another possible solution that is upgrade JDK from 11 to 17. Do you
recommend this solution?
On 2023/05/21 17:58:42 Greg Harris wrote:
> Vic,
>
> I found an open JIRA issue that previously reported this problem:
> https://issues.apache.org/jira/browse/KAFKA-10877 .
> I
Hi Greg,
I found another possible solution that is upgrade JDK from 11 to 17. Do you
recommend this solution?
Greg Harris 於 2023年5月22日 週一 上午1:59寫道：
> Vic,
>
> I found an open JIRA issue that previously reported this problem:
> https://issues.apache.org/jira/browse/KAFKA-10877 .
> I believe one
Vic,
I found an open JIRA issue that previously reported this problem:
https://issues.apache.org/jira/browse/KAFKA-10877 .
I believe one workaround is to use log4j 1.x, such as reload4j. Kafka
still relies on log4j 1.x until the planned upgrade to log4j 2.x in
kafka 4.0
Hello all, I have a Kafka cluster deployed with version 3.2.1 , JDK 11 and
log4j 2.18.0. I built my own Kafka image. One of my Kafka brokers is
experiencing CPU issues, and based on the jstack information, it seems that
log4j is causing the problem due to its usage of StackWalker. How to solve
