[MCOL-4031] Sorting code doesn't honor existing memory limits for ExeMgr. Created: 2020-06-02 Updated: 2021-02-04 Resolved: 2021-02-04 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | None |
| Affects Version/s: | 1.2.5, 1.4.4, 1.5.3 |
| Fix Version/s: | 6.1.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Roman | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Sprint: | 2021-2 |
| Description |
|
ExeMgr can go out of allowed memory limits doing sorting. Try to sort unreasonable amount of records that and instead of an error the system goes swapping then crashes or got killed by OOM. The intermediate workaround is to apply dedicated cgroup rules to ExeMgr. |
| Comments |
| Comment by Daniel Lee (Inactive) [ 2021-02-04 ] |
|
Build verified: 6.1.1 (drone #1620) Reproduced the issue in 5.5.1 and verified that it has been fixed in 6.1.1 VM has 4 gb of memory 5.4.1 top - 15:41:05 up 42 min, 2 users, load average: 7.00, 2.66, 1.93 MariaDB [tpch50]> select l_comment from lineitem order by l_comment; 6.1.1 top - 15:43:03 up 34 min, 2 users, load average: 1.27, 1.89, 1.70 MariaDB [tpch50]> select l_comment from lineitem order by l_comment; |