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

Set pause_on_next_bootstrap on an offline cluster #17904

Open
kwannoel opened this issue Aug 2, 2024 · 2 comments
Open

Set pause_on_next_bootstrap on an offline cluster #17904

kwannoel opened this issue Aug 2, 2024 · 2 comments

Comments

@kwannoel
Copy link
Contributor

kwannoel commented Aug 2, 2024

Support changing it in risingwave.toml. In certain cases the cluster is crash looping, and because in standalone modes the faults between different nodes are not isolated as they are all embedded, the cluster can't be easily recovered.

@github-actions github-actions bot added this to the release-1.11 milestone Aug 2, 2024
@BugenZhao
Copy link
Member

In certain cases the cluster is crash looping

I suppose you are referring to process panicking. Regular soft failures in streaming jobs should not affect the capability of setting system parameters with SQL interfaces.

@kwannoel
Copy link
Contributor Author

kwannoel commented Aug 2, 2024

In certain cases the cluster is crash looping

I suppose you are referring to process panicking. Regular soft failures in streaming jobs should not affect the capability of setting system parameters with SQL interfaces.

Yeah panic, regular soft failure will just trigger recovery, and meta + frontend should still be responsive.

@kwannoel kwannoel modified the milestones: release-2.0, release-2.1 Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants