The ``max_threads``, ``max_block_size``, ``max_download_threads`` and parallel parsing and formatting settings were declared in a ``<profile>`` block of ``config.d/low-resources.xml``. ClickHouse only reads profile settings from users configuration files, so they were silently ignored and the server used its defaults (one thread per core, larger blocks). Following the Plausible Community Edition change of ``v3.2.0`` (its pull request 265), ``config.d/low-resources.xml`` now keeps only the server setting ``mark_cache_size``, and the profile settings move to ``users.d/default-profile-low-resources-overrides.xml``, inside ``<profiles>``. ``system.settings`` now reports ``max_threads`` 1. Assisted-by: Claude:claude-opus-5-5
25 lines
692 B
YAML
25 lines
692 B
YAML
docker-image: docker.0k.io/clickhouse:24.12-alpine
|
|
#docker-image: clickhouse/clickhouse-server:24.12-alpine
|
|
|
|
data-resources:
|
|
- /var/lib/clickhouse
|
|
- /var/log/clickhouse-server
|
|
|
|
charm-resources:
|
|
- /etc/clickhouse-server/config.d/logs.xml
|
|
- /etc/clickhouse-server/config.d/ipv4-only.xml
|
|
- /etc/clickhouse-server/config.d/low-resources.xml
|
|
## Profile settings are only read from users.d (they were ignored when
|
|
## they lived in config.d/low-resources.xml).
|
|
- /etc/clickhouse-server/users.d/default-profile-low-resources-overrides.xml
|
|
|
|
provides:
|
|
event-db:
|
|
|
|
uses:
|
|
log-rotate:
|
|
constraint: recommended
|
|
auto: pair
|
|
solves:
|
|
disk-leak: "/var/log/clickhouse-server"
|