Harden distributed coordination for DataProvider 3.4.2 - #30
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
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.
Summary
Prepares DataProvider 3.4.2 as the qualified coordination foundation for later FeatureFramework replica-group work without adding any application-specific clustering API.
Changes
haunted-library-parent1.5.0 and prepare release version/tag metadata for 3.4.2<logical-node-id>/<process-id>owners and the difference betweenacquireandclaimDeliberately not included
ClusterService, replica-group, leader-selection, or FeatureFramework-specific APICoordinationDataAccessAPIValidation
CI runs normal unit/integration/coverage, shared Maven-policy validation, ShellCheck, and bundled Paper/Velocity platform acceptance. The new
RedisCoordinationFencingITis exercised by the existingintegration-testsprofile with Docker/Testcontainers.The first CI run exposed a real HauntedPlatform-1.5 alignment issue: DataProvider's Surefire
-javaagentpath referenced the inherited Mockito version before that artifact was guaranteed to be resolved in modules that do not directly depend on Mockito. The PR now declares Mockito as a Surefire plugin dependency, preserving the existing agent model without pinning an obsolete version.Commit structure
chore(build): align DataProvider 3.4.2 with HauntedPlatform 1.5test(coordination): qualify fenced lease semanticsdocs(coordination): document fenced lease semanticsdocs: add distributed coordination guide to indexdocs(release): prepare DataProvider 3.4.2 documentationchore(build): inherit shared Maven policy from HauntedPlatformfix(build): resolve Mockito agent through Surefire