We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
So using consul's kv store we can do more in terms of orchestration than just leader election (if we even want to go that route)
but basically /service/toshi/leader true
/service/toshi/leader true
whichever node gets the session lock on this is the leader then nodes can join the cluster and announce their address perhaps via something like
/service/toshi/cluster/tn1 hostname:port /service/toshi/cluster/tn2 hostname:port
/service/toshi/cluster/tn1 hostname:port
/service/toshi/cluster/tn2 hostname:port
So on so forth, I don't have any particular attachment to this method, but just something to get started with.
The text was updated successfully, but these errors were encountered:
Off the top of my head:
Sorry, something went wrong.
No branches or pull requests
So using consul's kv store we can do more in terms of orchestration than just leader election (if we even want to go that route)
but basically
/service/toshi/leader true
whichever node gets the session lock on this is the leader then nodes can join the cluster and announce their address perhaps via something like
/service/toshi/cluster/tn1 hostname:port
/service/toshi/cluster/tn2 hostname:port
So on so forth, I don't have any particular attachment to this method, but just something to get started with.
The text was updated successfully, but these errors were encountered: