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
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 create table request to stop waiting and returns an error.
There is a network partition between the frontend node and the meta node for 10 minutes.
I think the call stack will be like
frontend request (protocol layer)
- create table handler
- RPC call to Meta <-- waiting here
Perhaps the RPC call to Meta didn't fail as expected. Let's dive into it.
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: