Skip to content
This repository has been archived by the owner on Apr 2, 2023. It is now read-only.

High CPU usage when using kafka-clients:3.3.1 #146

Open
kishorepurushothaman20 opened this issue Nov 23, 2022 · 4 comments
Open

High CPU usage when using kafka-clients:3.3.1 #146

kishorepurushothaman20 opened this issue Nov 23, 2022 · 4 comments

Comments

@kishorepurushothaman20
Copy link

kishorepurushothaman20 commented Nov 23, 2022

Hi,

We have a Dropwizard app (dropwizard-core:2.1.4) which uses zipkin-core:2.0.16-1 with 'kafka' collector. When using it along kafka-clients:3.3.1 we are able to see a high CPU usage but the same behaviour does not apply when using kafka-clients:3.2.3.
On using a profiler we are able to see a worker thread stuck in Runnable state forever and is not going to the waiting state after the traces are published. The thread goes to Runnable state and stuck there forever when an initial API request hits one of our endpoints. JDK used is Corretto 17.0.5

Below image using,

<dependency>
    <groupId>org.apache.kafka</groupId>
    <artifactId>kafka-clients</artifactId>
    <version>3.3.1</version>
</dependency>

image

Below image using,

<dependency>
    <groupId>org.apache.kafka</groupId>
    <artifactId>kafka-clients</artifactId>
    <version>3.2.3</version>
</dependency>

image

Can you help in shedding some light on this or can it be taken as bug?
If it is not a bug can I get some compatibility matrix for dropwizard-zipkin bundle with kafka-clients?

Regards,
Kishore

@github-actions
Copy link

This issue is stale because it has been open 90 days with no activity. Remove the "stale" label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the Stale label Feb 22, 2023
@kishorepurushothaman20
Copy link
Author

Any updates on this issue?

@jplock
Copy link
Member

jplock commented Feb 22, 2023

I don't currently use Zipkin or Kafka to know how to replicate this or debug it.

@github-actions github-actions bot removed the Stale label Feb 23, 2023
@kishorepurushothaman20
Copy link
Author

No fix as of now is it?
Should this be closed then? @jplock

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants