Add an etcd backend option to choose linearizable reads#97
Open
tanguy-ortolo wants to merge 1 commit intoHeavyHorst:masterfrom
Open
Add an etcd backend option to choose linearizable reads#97tanguy-ortolo wants to merge 1 commit intoHeavyHorst:masterfrom
tanguy-ortolo wants to merge 1 commit intoHeavyHorst:masterfrom
Conversation
This is optional, and default to previous behaviour, which is to use linearizable reads.
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
1 participant
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.
Remco uses easyKV, which uses linearizable reads with both etcd v2 and etcd v3. This comes with a delay cost.
This PR adds an option to choose linearizable reads. It depends on an easyKV PR, so it will first require tagging a new easyKV version and updating go.mod to use it.