[MCOL-5187] OOM happening when querying large datasets and using distinct Created: 2022-08-10 Updated: 2023-12-15 |
|
| Status: | Stalled |
| Project: | MariaDB ColumnStore |
| Component/s: | None |
| Affects Version/s: | 22.08.1, 6.4.6 |
| Fix Version/s: | 23.10 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Kugimiya | Assignee: | Roman |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | SQL, query, triage | ||
| Environment: |
ububts 20.04 LTS |
||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Description |
|
I set TotalUmMemory to 25%, but ExeMgr use far beyond usage memory. 1. select distinct columnA, columnB, columnC from table. 1. is OOM, I think 1. and 2. are similar query. |
| Comments |
| Comment by Roman [ 2022-08-19 ] |
|
Thx for your suggestion. We will look into implementing it. |
| Comment by Kugimiya [ 2022-08-21 ] |
|
Thanks for your answer. Yes, I did. DISTINCT problem is using memory without getting an error. I think that DISTINCT implementation should check TotalUmMemory. |
| Comment by Roman [ 2022-08-22 ] |
|
It surely must obey the limitations of TotalUmMemory. I will look into the difference b/w distinct and group by in terms of memory consumption limitation. |
| Comment by JiraAutomate [ 2023-12-15 ] |
|
Automated message: |