Fix Raft member rejoining and rolling upgrade compatibility - #300
Open
guillaume-chervet wants to merge 3 commits into
Open
guillaume-chervet wants to merge 3 commits into
guillaume-chervet wants to merge 3 commits into
Conversation
Signed-off-by: Guillaume Chervet <guillaume.chervet@gmail.com>
Signed-off-by: Guillaume Chervet <guillaume.chervet@gmail.com>
Signed-off-by: Guillaume Chervet <guillaume.chervet@gmail.com>
8 tasks
Author
|
@dotnet-policy-service agree |
guillaume-chervet
marked this pull request as ready for review
September 16, 2026 07:20
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
Fixes #299. Downstream validation: SlimPlanet/SlimFaas#403.
Based on
develop(f10ace6), per CONTRIBUTING.md. Local package experiments include those existing development-branch changes as well as this PR.This fixes three blockers found while upgrading a three-node SlimData cluster from DotNext 6.6.0 to 6.7.2:
A removed live member receives HTTP 500 for AppendEntries when the leader setter reads its faulted election task. Handle that completed task without reading
Result, and restore the follower state and fresh leadership waiters when the previously ready member is added again.Existing WAL metadata pages are interpreted using the current OS page size, changing page numbering on 16 KiB-page hosts. Read and validate the existing page sizes before opening WAL files, preserve that layout, and allow private buffers smaller than an OS page. New logs keep the current default. Invalid or inconsistent page sizes fail before files are opened/resized.
New Raft HTTP headers break mixed-version operation with 6.6.0: missing
X-Raft-State-Versionnow means implicit version zero; missingX-Raft-Last-Indexfalls back to the legacy one-entry backtracking behavior. Explicit malformed headers still fail parsing.There are no public API changes, new dependencies or on-disk rewrites. The change preserves both legacy 4 KiB pages and logs already created with larger metadata pages.
Validation
6.7.2-slimdata.402, including the existing re-addition test and a real 6.6.0 compacted snapshot/WAL fixture that fail against the published 6.7.2.6.7.2-slimdata.402.2, commit750c57f), all 1,545 downstream .NET tests pass (also after NuGet centralization, including embedded UI builds) and native AOT publication passes with unchanged baseline third-party warnings.developbuild; they do not isolate these three fixes. Downstream adoption remains blocked.Test commands:
This contribution is AI-assisted (Codex); the
ai_assistedlabel is required by CONTRIBUTING.md. Adding that label was denied for the contributor account; a maintainer needs to apply it. Built and tested with .NET SDK 10.0.300 on macOS ARM64. Existing compiler/analyzer warnings in untouched code are unchanged.