[MCOL-5500] cgroups v2 support with version autodetection Created: 2023-05-25  Updated: 2023-07-01  Resolved: 2023-06-21

Status: Closed
Project: MariaDB ColumnStore
Component/s: ExeMgr, PrimProc
Affects Version/s: 23.02.3
Fix Version/s: 23.02.4

Type: New Feature Priority: Major
Reporter: Roman Assignee: Roman
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Problem/Incident
causes MCOL-5489 Query Cache Overload Causing PrimProc... Closed
causes MCOL-5518 Remove redundant calls to CGRoupConfi... Open
Sprint: 2023-6
Assigned for Review: Leonid Fedorov Leonid Fedorov
Assigned for Testing: Daniel Lee Daniel Lee (Inactive)

 Description   

MCS supports cgroup v1 only with no proper checks for values that cgroups v1 returns,e.g for memory limits. There were some combinations of kernel versions/container runtimes that has unreasonable values for max memory available for containers. The fact the values changes complicates the erroneous values detection.

This patch for the issue adds cgroups v2 support and also applies some sanity check for values reported by cgroups v1 hierarchy.

4QA cgroups hardware limits detection is disabled by default so one has to set SystemConfig.CGroup, e.g.

<SystemConfig>
   <CGroup>./</CGroup>
</SystemConfig>

This sets CGroup to the default one unless one sets a named CGroup. Both should be tested though.


Generated at Thu Feb 08 02:58:20 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.