-
Notifications
You must be signed in to change notification settings - Fork 526
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
v1.9.0-rc chaos-mesh case failed #16706
Comments
In both "create table stuck" cases, the chaos we ingested include
There is a network partition between the frontend node and the meta node for 10 minutes. We expect the |
Check the await-tree dump file and didn't find anything wrong. The streaming was running normally. I guess the problem was because no one notifies the frontend
I think the call stack will be like
Perhaps the |
We reran those two for v1.9.0-rc-1. One hit this again https://buildkite.com/risingwave-test/chaos-mesh/builds/829#018f7135-e456-440d-8212-0d6b161e9dee. Another one passed https://buildkite.com/risingwave-test/chaos-mesh/builds/830. So the reproducible rate is quite high but not 100% |
Describe the bug
https://buildkite.com/risingwave-test/chaos-mesh/builds/826#018f659e-814b-43fd-9534-32cadf65a1a4
https://buildkite.com/risingwave-test/chaos-mesh/builds/825#018f659e-81e8-42f4-8a0d-238aa91fc23b
Seems like the test stuck at creating table
Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
v1.9.0-rc
Additional context
No response
The text was updated successfully, but these errors were encountered: