Conversation
- refactor support code in agent and server to separate lib mods for cleaner tracing - locks_server sends only one notification per involved agent - locks_server keeps a global vsn counter to ensure strictly increasing versions - locks_leader maintains an election vector based on lock info - signal leader_uncertain or ensure_sync more often, esp. if the vector info indicates inconsistency. - moved example code to fit better with rebar3 - remove rebar2-specific compilation in locks_leader_SUITE
Owner
Author
|
Note: some issues identified. Still debugging. |
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 PR tries to address both issues #37 and #30.
locks_leader, to facilitate debugging should the election process hang.locks_leaderto better keep up with the status of the locking process, andleader_uncertainis triggered anytime the vectors don't match.