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

Add support for clusters with a disabled config db #2059

Open
gm42 opened this issue Jun 12, 2024 · 1 comment
Open

Add support for clusters with a disabled config db #2059

gm42 opened this issue Jun 12, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@gm42
Copy link
Contributor

gm42 commented Jun 12, 2024

What would you like to be added/changed?

A FoundationDB cluster can be run with the config db disabled (--no-config-db passed to fdbserver processes); however when operator would issue the coordinators command via fdbcli, this is expected to result in a hanging command (for reference, see apple/foundationdb@cd2bbff and apple/foundationdb@1a33515).

The enhancement request is to allow in some way to run clusters with the config db disabled; this originally came up while discussing mitigations for N2_ConnectError to ghost coordinator IPs, see this forum thread.

@gm42 gm42 added the enhancement New feature or request label Jun 12, 2024
@sfc-gh-ljoswiak
Copy link

I submitted apple/foundationdb#11491 to fix the client-side hang issue. This will remove the need to specify any extra flags on clients when the configuration database is disabled server side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants