[WIP] pass token ring view with mutations/reads, and verify #606
Conversation
This file contains 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
rhuffy
changed the title
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.
It is possible for nodes to have inconsistent views of the token ring, and still accept reads/writes.
Previously, we introduced
InvalidMutations, where a node would check if it owned a token before applying the mutation. However, that implementation fails when the receiving node itself has an incorrect view of the ring.This PR attempts to address these cases by including the coordinator's view of the ring in Mutation and Read Messages. When handling these verbs, nodes now validate that they have the same view of the ring as the coordinator.