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.

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

bug: recovery failure #20544

Open
chenzl25 opened this issue Feb 20, 2025 · 0 comments
Open

bug: recovery failure #20544

chenzl25 opened this issue Feb 20, 2025 · 0 comments
Labels
type/bug Something isn't working
Milestone
release-2.3

Comments

@chenzl25
Copy link
Contributor

Describe the bug

The cluster failed to recover itself until manually restarted. What we found is that the compute node throws an error like receiver for (64694, 59874) has already been taken which is unexpected. This indicates that the plan generated by our meta scheduler is inconsistent because it generates a duplicate edge for two actors.

Error message/log

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response
@chenzl25 chenzl25 added the type/bug Something isn't working label Feb 20, 2025
@github-actions github-actions bot added this to the release-2.3 milestone Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/bug Something isn't working
Projects
None yet
Milestone
release-2.3
Development

No branches or pull requests
1 participant
@chenzl25