drrtuy,

Docker image mariadb/enterprise-columnstore-dev:develop-23.02- used (taken at 05 Jul 2023).

docker run command like:

docker run -m 3GB --kernel-memory 3GB --memory-reservation 3GB --memory-swap 3GB --hostname=mcs3 --name mcs3 -d mariadb/enterprise-columnstore-dev:develop-23.02-

tested limits: 3, 5, 6, 7+(no limits) Gbs

query:
SELECT * INTO OUTFILE '/tmp/result.txt' FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
LINES TERMINATED BY '\n' FROM flights;

result: 3 and 5 Gbs - error: ERROR 1815 (HY000): Internal error: MCS-2004: Cannot connect to ExeMgr.
6 and 7+ Gbs - success

4 queries running in parallel on 6GB container raise error.
4 queries running in parallel on 7+GB container succeeded.

Using VirtualBox the results are different.
For same query and with memory limited to 6GB and 4GB, PrimProc is using almost all free memory, but OOM killer not happened and query succeeded.
For 6GB, htop shows total RAM as 5.55GB , PP using 5.1GB
For 4GB, htop shows total RAM as 3.55GB , PP using 3GB

Also 2 queries in parallel succeeded at both configs.

alexey.vorovich
Roman require restart for some debug purposes (change config I think).

drrtuy please review above and let me know what is next step to debug MCS in container

At the moment I'm working on creating test environment with docker and systemd enabled.

drrtuy
Under linux host, query succeeded in container with 3GB limit.

Only 2 queries in parallel fail.