-
Notifications
You must be signed in to change notification settings - Fork 25k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure logging for async fetch causes Network threads to be BLOCKED #57501
Comments
The |
There's nothing actionable here so I am closing this. Please fill out the bug report template in full when reporting apparent bugs. We need significantly more information than you have provided here before we can even start to analyse a bug report. A stack trace from a single thread is rarely of any use and this one doesn't indicate anything particularly surprising happening. |
I thought the bug is, it's not right to have a logging overhead on Network threads. Can you please correct me if I am wrong @DaveCTurner . The stack trace shows that and I have the full thread dump https://gist.github.com/Bukhtawar/1b9e1ad07958d684a8d9ebce3fcb4889 I'll share the logs if I'm unable to repro
I am working on that if you can please bear with me. |
On this particular case since Do you think this is the expected and the desired behaviour @DaveCTurner ? |
If you see the implementation of the transport_worker its actually doing another IO. See
|
Below is the thread dump indicating
transport_worker
threads beingBLOCKED
, there were multiple threads in this state. Although this happened on 6.8 but I believe it would still happen on later versions too.The text was updated successfully, but these errors were encountered: