[CORE] Avoid driver oom caused by unnecessary metadata columns in huge number of splitinfos#11899
Open
taiyang-li wants to merge 1 commit intoapache:mainfrom
Open
[CORE] Avoid driver oom caused by unnecessary metadata columns in huge number of splitinfos#11899taiyang-li wants to merge 1 commit intoapache:mainfrom
taiyang-li wants to merge 1 commit intoapache:mainfrom
Conversation
taiyang-li
changed the title
|
Run Gluten Clickhouse CI on x86 |
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 changes are proposed in this pull request?
When scanning tens of millions of files, the driver may run out of heap memory during split construction.
Currently we always generate per-file metadata maps (InputFileName / InputFileBlockStart / InputFileBlockLength) for each split, even if the query does not reference these metadata columns. This causes a large number of
HashMapinstances to be kept in memory and may trigger OOM in the planner.How was this patch tested?
Manully tested in production environment
Was this patch authored or co-authored using generative AI tooling?
Generated-by: trae