Bump JasperFx to 2.21.1 (per-tenant HWM poll cadence, jasperfx#492/#493)#3335
Merged
Conversation
#492/#493) JasperFx 2.21.1 drives the vectorized per-tenant high-water poll from the daemon's own SlowPollingTime timer instead of solely from store-global mark changes, so a lagging tenant appending below the global max converges without unrelated tenant activity. Epic #486 (WS1 residue). Full wolverine.slnx Release build + MartenTests.Distribution folder green locally (31 tests, net9.0). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 9, 2026
Merged
This was referenced Jul 13, 2026
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.
Consumes JasperFx 2.21.1 (#493): the vectorized per-tenant high-water poll now runs on the daemon's own
SlowPollingTimetimer rather than solely on store-global mark publications, so a lagging tenant appending below the global max converges without unrelated activity. Part of epic #486 (WS1 residue); the marten twin is marten#4876.No Wolverine code changes — the failover e2e here never needed the seed-above-global-mark workaround that the marten dynamic-lifecycle tests carried.
Verified locally: full
wolverine.slnxRelease build + theMartenTests.Distributionfolder (31 tests, net9.0) green.🤖 Generated with Claude Code