Repository navigation
discovery for coyote peers - #55
Merged
Merged
Conversation
svix-jbrown
force-pushed
the
jbrown/raft-disco
branch
from
January 31, 2026 01:08
86d8a1a to
d3a0017
Compare
svix-jplatte
pushed a commit
that referenced
this pull request
Apr 9, 2026
svix-jbrown
added a commit
that referenced
this pull request
Apr 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds some basic discovery for cluster bootup, based on a configured list of seed nodes.
When a new node comes up, it reaches out to all of the seed nodes. If there is a single cluster containing some subset of them, it attempts to join that cluster. If none of them are in a cluster, it attempts to initialize a new cluster. This is somewhat racy, because if you launch several nodes at the same time they all might try to initialize and you'd end up with 3 one-node clusters; I'll have work on improving that, but I wanted to get //something// out.
This also changes the config system. I like the idea of using a nested config (where cluster config is in its own Table), but this doesn't play super-well with the
configmodule. I reconfigured it to support nested config for environment variables (separated by the:character), which required fixing up thedotenvycrate to also support such keys. The SHA here is allan2/dotenvy#161 rebased on top 0.15.