#2974: Add hash-based journal selection for improved ledger distribution #4709
+123
−3
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.
Main Issue: #2974
Motivation
When multiple journals are configured, BookKeeper selects a journal using ledgerId % numJournals. This works well when
ledger IDs are random or sequential, but produces poor distribution when ledger IDs follow strided patterns (e.g., when
multiple clients allocate IDs from disjoint ranges). Uneven journal utilization can cause hotspots and reduce write
throughput.
Changes
patterns