This repository was archived by the owner on Feb 18, 2025. It is now read-only.
Raft reverse proxy API calls to leader #408
Merged
Conversation
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
added 13 commits
February 12, 2018 12:04
…d loaded in snapshot; used by reverse proxy
|
|
This works well. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Closes #245
This PR introduces a reverse proxy for API calls such that:
when running Raft
when calling selected
/api/...calls on a non-leaderwhen the node is a valid follower (can see the leader)
the node will reverse proxy the request to the leader
excluded from reverse-proxy: queries like
status,raft-health,raft-state,lb-checketc., which are node-specific.This will allow querying any valid raft node as well as making changes, refactoring, etc.
Introduced:
/api/raft-health: a health/readiness check to confirm the node is a healthy part of the raft group.