[#400] Draft increment: ChronicleMap - Max Entry Limit reduces after removing few entries - #613
Draft
peter-lawrey wants to merge 1 commit into
Draft
Conversation
Replace the undersized clear-and-readd experiment with an executable fixed-seed harness using the reported 61,500-entry capacity, 500-byte ByteBuffer keys, 5,120-byte values, and repeated partial removal and refill. Record per-segment occupancy, byte and entry pressure, tiers, free chunks, failing segments, cross-version results, raw-output hashes, and exact JDK 8/21 runner commands. Add quiescence, validation, cutover, and rollback requirements to the rebuild guidance. The tiering-enabled controls do not reproduce the original issue body. The evidence establishes only the associated tiering-disabled mechanism and is explicitly documented as investigation rather than a fix. Refs #400
peter-lawrey
force-pushed
the
fix/Chronicle-Map-400-document-capacity-loss-limitation
branch
from
August 22, 2026 11:00
444eaa5 to
3187c22
Compare
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.
What this draft demonstrates
Local
125f5ac8documents measured capacity-loss mechanics/workarounds; it does not implement tier reclamation.Why publish it now
This makes the local partial/design/research work for #400 reviewable without claiming that the broader issue is complete. Review can now decide whether to keep the increment, change direction, or stop the work.
Known gap
Publish the evidence/docs increment, then close/rescope unless a funded allocator design with churn benchmarks is accepted.
Review status
Draft partial — do not mark ready or close the issue until the known gap is resolved or explicitly split.
Validation
git diff --checkagainstea: passed..pr/scaffolding and local workspace paths: removed.Tracking
Related to #400. This PR deliberately does not use a closing keyword.