Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Modify parallel hashagg spill doc #17901

Merged
merged 6 commits into from
Jun 27, 2024
Merged

Modify parallel hashagg spill doc #17901

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
2637fd7
init
xzhangxian1008 Jun 17, 2024
e258097
tweaking
xzhangxian1008 Jun 17, 2024
3dad621
Merge branch 'master' into hashagg-8.2
Oreoxmt Jun 17, 2024
f5f9444
refine wording
Oreoxmt Jun 17, 2024
46204f3
refine wording
Oreoxmt Jun 18, 2024
224fcb3
Apply suggestions from code review
Oreoxmt Jun 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion configure-memory-usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,7 @@ TiDB supports disk spill for execution operators. When the memory usage of a SQL

- The disk spill behavior is jointly controlled by the following parameters: [`tidb_mem_quota_query`](/system-variables.md#tidb_mem_quota_query), [`tidb_enable_tmp_storage_on_oom`](/system-variables.md#tidb_enable_tmp_storage_on_oom), [`tmp-storage-path`](/tidb-configuration-file.md#tmp-storage-path), and [`tmp-storage-quota`](/tidb-configuration-file.md#tmp-storage-quota).
- When the disk spill is triggered, TiDB outputs a log containing the keywords `memory exceeds quota, spill to disk now` or `memory exceeds quota, set aggregate mode to spill-mode`.
- Disk spill for the Sort, MergeJoin, and HashJoin operators is introduced in v4.0.0; disk spill for the non-concurrent algorithm of the HashAgg operator is introduced in v5.2.0; disk spill for the concurrent algorithm of the HashAgg operator is introduced in v8.0.0.
- Disk spill for the Sort, MergeJoin, and HashJoin operators is introduced in v4.0.0; disk spill for the non-concurrent algorithm of the HashAgg operator is introduced in v5.2.0; disk spill for the concurrent algorithm of the HashAgg operator is introduced in v8.0.0 and becomes GA in v8.2.0. User could close or open parallel HashAgg spill function by system variable `tidb_enable_parallel_hashagg_spill`(This is a temporary system variable and will be deleted in the future).
- When the SQL executions containing Sort, MergeJoin, HashJoin, or HashAgg cause OOM, TiDB triggers disk spill by default.

> **Note:**
Expand Down
Loading