Skip to content

Conversation

@davissp14
Copy link
Contributor

@davissp14 davissp14 commented Jan 26, 2023

This works to drastically reduce our dependency on Consul for basic cluster management.

Outside of configuration management, the only thing we leverage consul for is to set an initialization flag that lets future members coming up know whether the cluster exists or not. If the flag is not set, then it's fairly safe to assume that it should register itself as primary. It's possible there's a race condition here, but given how PG provisioning works in Fly this shouldn't be an issue.

Given how we use the initialization flag, clusters will not be able to horizontally scale in the event consul goes down. However, everything aside from configuration management will continue to work normally.

Things this PR does not address

We still need to identify and fence a failed primary coming back from the dead.

@davissp14 davissp14 changed the title WIP - Rework Reduce usage of Consul. Jan 26, 2023
@davissp14 davissp14 merged commit dfb4e6d into master Jan 27, 2023
@davissp14 davissp14 deleted the rework branch February 25, 2023 01:59
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.

2 participants