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: frontend can't connect to CN sometimes when CNs have been restarted #14576

Open
chenzl25 opened this issue Jan 15, 2024 · 4 comments
Open
Assignees
Labels
no-issue-activity type/bug Something isn't working

Comments

@chenzl25
Copy link
Contributor

Describe the bug

Frontend can't connect to CN sometimes when CNs have been restarted until we restart the frontend node. Need to find a way to reproduce this issue.

Error message/log

No response

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 Jan 15, 2024
@github-actions github-actions bot added this to the release-1.7 milestone Jan 15, 2024
@lmatz
Copy link
Contributor

lmatz commented Jan 15, 2024

#14030 chaos mesh can reproduce it sometimes

@rotten
Copy link

rotten commented Feb 26, 2024

Restarting the frontend after it gets into this state does not help it recover. Restarting the meta node after this happens does seem to resolve it.

@rotten
Copy link

rotten commented Feb 26, 2024

... but only if I shutdown the old meta node completely first. Simply bringing up a second meta and tearing down the old one doesn't seem to work.

I could update the "graceful shutdown" script on the compute node to also trigger a meta restart, but that wouldn't cover the scenario when a compute node simply crashes.

@fuyufjh fuyufjh changed the title bug:frontend can't connect to CN sometimes when CNs have been restarted bug: frontend can't connect to CN sometimes when CNs have been restarted Mar 6, 2024
@chenzl25 chenzl25 removed this from the release-1.9 milestone May 14, 2024
Copy link
Contributor

github-actions bot commented Aug 1, 2024

This issue has been open for 60 days with no activity.

If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean.
Don't worry if you think the issue is still valuable to continue in the future.
It's searchable and can be reopened when it's time. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-issue-activity type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants