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

Fix/single node status #2581

Merged
merged 2 commits into from
Feb 19, 2020
Merged

Fix/single node status #2581

merged 2 commits into from
Feb 19, 2020

Conversation

janl
Copy link
Member

@janl janl commented Feb 19, 2020

Really fix #2557

SingleNodeConfig = config:get_boolean("couchdb", "single_node", false),
case SingleNodeConfig of
true ->
chttpd:send_json(Req, 200, {[{state, single_node_enabled}]});
Copy link

@gesellix gesellix Feb 19, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

setup:is_single_node_enabled(Dbs) isn't necessary, because we expect the single_node setup to work?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gesellix yeah it’s a tiny bit of a fudge, I hoped we can get away with it :)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if this ends up causing an issue in practice, we can add another clause there, but then we also need to invent a new state like single_node_pending or something and I didn’t want to get this in this late in the game.

@wohali wohali merged commit 26f9366 into master Feb 19, 2020
@wohali wohali deleted the fix/single-node-status branch February 19, 2020 23:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unexpected cluster state for single node config
3 participants