-
Notifications
You must be signed in to change notification settings - Fork 595
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
bug: stuck when dropping sink #7639
Comments
Looks like we're stuck in Will #7637 be related? |
I guess not? #7637 was a deterministic bug while this one looks accidental.
Can you give some hint on how to investigate on this? I am trying to enable verbose_async_trace now. |
I've quickly checked the code of the |
Haha, that screenshot was updated by me after I set aync_stack_trace to "verbose" |
I've tried to reproduce the bug both in our local environment and in the CI environment, but failed. The CI environment used to be able to reproduce the bug, but now we have run under the same benchmark setting for many times, but still cannot reproduce it. I suspect that the bug has been fixed by some PR by the way, and I have added necessary logs to trace the progress of sync. If there is some pending sync task, we can see from the log. I think we can hold this issue and observe whether the bug happens again in the future. |
It seems that this bug has not been seen for several months? |
I think so. Maybe we can close this issue? |
Agree. Let's close it now. |
Describe the bug
Create sink (nexmark_q4), wait for a while, and then drop it. The client was stuck then.
Observations:
To Reproduce
Failed to reproduce it in my environment...
Expected behavior
No response
Additional context
The text was updated successfully, but these errors were encountered: