8000 shared source: potential panic bug · Issue #21769 · risingwavelabs/risingwave · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

shared source: potential panic bug #21769

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.

Sign up for GitHub

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

Jump to bottom
Open
xxchan opened this issue May 8, 2025 · 0 comments
Open

shared source: potential panic bug #21769

xxchan opened this issue May 8, 2025 · 0 comments
Assignees
@xxchan
Labels
type/bug Type: Bug. Only for issues.

Comments

@xxchan
Copy link
Member
xxchan commented May 8, 2025 •
edited
Loading

panic 1

https://www.notion.so/risingwave-labs/1c2f0d69cb768054b52ccac03746058d

v2.3

"panicked at src/stream/src/task/barrier_manager/progress.rs:240:17:
should not update consuming progress at invalid state: DoneConsumingUpstreamTableOrSource(0)"

flow was like this:
DB1:
source1 -> sink1 -> table1 -> subscription1
DB2:
source2 -> sink2 -> table2 -> subscription2
DB3:
source3 -> sink3 -> table3 -> subscription3
DB4:
source4 -> sink4 -> table4 -> subscription4
DB5:
[table sink1 + table sink2] -> join table2
[table sink1 + table sink3] -> join table3
[table sink1 + table sink4] -> join table4

Panic 2

thread 'rw-streaming' panicked at src/stream/src/executor/source/source_backfill_executor.rs:165:51:
called `Option::unwrap()` on a `None` value
stack backtrace:

https://risingwave-community.slack.com/archives/C083UG9M612/p1746418799563789

Running version 2.3.0. I keep dropping the sources, sinks, and tables mentioned in the logs but this keeps happening and crashing the compute nodes. If I restart the meta node it also starts crashlooping and is unrecoverable. I currently have one cluster in that state where I cannot start it back up. And now on a brand new cluster I made on friday I started rebuilding all the sources and tables and after the node crashed (I think due to OOMKill but this happened while I was away) it then entered this statte where after it recovers it crashes again with this error. However, the meta node has not crashed and is still functioning so I can still execute queries against the cluster.
@xxchan xxchan self-assigned this May 8, 2025
@xxchan xxchan added the type/bug Type: Bug. Only for issues. label May 8, 2025
@github-actions github-actions bot added this to the release-2.4 milestone May 8, 2025
@xxchan xxchan removed this from the release-2.4 milestone May 8, 2025
@xxchan xxchan mentioned this issue May 9, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xxchan xxchan

Labels
type/bug Type: Bug. Only for issues.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@xxchan
0