-
Notifications
You must be signed in to change notification settings - Fork 354
fix: enforce fair memory share per reservation #5466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
peterxcli
wants to merge
1
commit into
apache:main
Choose a base branch
from
peterxcli:fix/fair-memory-share-per-reservation
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[P2] Preserve the aggregate configured pool limit
This replaces the only aggregate admission bound with a per-reservation check. With
spark.memory.offHeap.size=64mandspark.comet.exec.memoryPool.fraction=0.5,pool_sizeis 32 MiB. A can register and reserve 24 MiB; after B registers, B's request for 16 MiB now passes (0 + 16 <= 32 / 2), leaving 40 MiB reserved against the configured 32 MiB budget. The base rejects B's request. Similarly,new_empty()shares its consumer registration while starting a separate size counter, so sibling reservations can collectively exceed the budget; DataFusion's native sort merge uses this pattern.Spark's JVM memory manager only applies its larger off-heap budget, not Comet's fraction, so it can grant these requests. This consumes the headroom that the tuning guide explicitly reserves to avoid OOM from untracked allocations. Please retain the corrected requester check and add a separate aggregate
state.usedversuspool_sizebound; this does not require the spillability-policy change in #5465.Both excess-allocation sequences were reproduced against unchanged head/base pool code in a harness with mocked JNI grants; Spark's larger backing limit was verified separately in source.