Skip to content
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: recover_backfill_state panic #19138

Closed
zwang28 opened this issue Oct 26, 2024 · 2 comments
Closed

bug: recover_backfill_state panic #19138

zwang28 opened this issue Oct 26, 2024 · 2 comments
Assignees
Labels
type/bug Something isn't working
Milestone

Comments

@zwang28
Copy link
Contributor

zwang28 commented Oct 26, 2024

Describe the bug

The stream job being backfilled is SINK INTO TABLE. It includes NOW.

"panicInfo": "panicked at src/stream/src/executor/backfill/no_shuffle_backfill.rs:607:13:\nassertion left == right failed\n left: true\n right: false"

The compute node has been scaled down from 6C to 2C. I suspect it's related because the assertion mentions: All vnode partitions should have same state (no scale-in supported).

Error message/log

No response

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

v2.0.2

Additional context

No response

@zwang28 zwang28 added the type/bug Something isn't working label Oct 26, 2024
@github-actions github-actions bot added this to the release-2.2 milestone Oct 26, 2024
@zwang28
Copy link
Contributor Author

zwang28 commented Oct 26, 2024

Currently scaling is not supported for background backfilling job

So this is an expected error.
It will be better if we don't have to drop the affected sinks to recover the cluster. @kwannoel

@kwannoel
Copy link
Contributor

Opened an issue here #19142 for the corresponding feature. Closing as this is not a bug.

@kwannoel kwannoel closed this as not planned Won't fix, can't repro, duplicate, stale Oct 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants