You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 2, 2023. It is now read-only.
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
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
The text was updated successfully, but these errors were encountered:
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,
Below image using,
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
The text was updated successfully, but these errors were encountered: