Clickhouse still not respecting CPUShares in the latest version
007developforfun opened this issue · 2 comments
ClickHouse server version 22.5.1 revision 54455
System Cores : 32
We did the following steps:
sudo systemctl set-property clickhouse-server.service CPUShares=50 MemoryLimit=12000M
sudo systemctl daemon-reload
sudo systemctl stop clickhouse-server
sudo systemctl start clickhouse-server
sudo systemctl status clickhouse-server
● clickhouse-server.service - ClickHouse Server (analytic DBMS for big data)
Loaded: loaded (/usr/lib/systemd/system/clickhouse-server.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/clickhouse-server.service.d
└─50-CPUShares.conf, 50-MemoryLimit.conf
Active: active (running) since Wed 2022-08-10 06:35:47 PDT; 1 day 21h ago
Main PID: 26362 (clckhouse-watch)
Tasks: 272
Memory: 6.0G (limit: 11.7G)
CGroup: /system.slice/clickhouse-server.service
├─26362 clickhouse-watchdog --config=/etc/clickhouse-server/config.xml --pid-file=/run/clickhouse-server/clickhouse-server.pid
└─26363 /usr/bin/clickhouse-server --config=/etc/clickhouse-server/config.xml --pid-file=/run/clickhouse-server/clickhouse-server.pid
cat /etc/systemd/system/clickhouse-server.service.d/50-CPUShares.conf
[Service]
CPUShares=50
top:
%Cpu(s): 13.7 us, 4.6 sy, 0.0 ni, 81.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st
KiB Mem : 13172606+total, 1017936 free, 16944072 used, 11376405+buff/cache
KiB Swap: 33554428 total, 33554428 free, 0 used. 10994254+avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
26363 clickho+ 20 0 41.4g 989.2m 403440 S 587.1 0.8 16605:34 clickhouse-server
Clickhouse-server seems to be consuming 587.1% even after setting the CPUShare to 50, where as we expect to stay below 100%.
Please help in fixing this or provide clarification in case we are missing something.
Thanks,
Ketan
Hi! I am sorry to disappoint you, but this project is no longer developed. Thus I wouldn't expect any assistance for your problem from its maintainers. Some loghouse users still might help, though…
P.S. Is your issue actually related to loghouse? It sounds like some issue with Clickhouse DBMS itself, not loghouse.
Apologies. The issue is related to Clickhouse DBMS. Wrong forum.