Skip to content

fix(clickhouse): wire up prod log-TTL config that was never mounted - #254

Open
MostafaMoradii wants to merge 1 commit into
mainfrom
fix/clickhouse-log-ttl-config
Open

MostafaMoradii wants to merge 1 commit into
mainfrom
fix/clickhouse-log-ttl-config

Conversation

@MostafaMoradii

Copy link
Copy Markdown
Collaborator

Summary

  • deploy/compose/clickhouse/config.d/zz-eveys-prod.xml and users.d/zz-eveys-async-insert.xml were written after the 2026-08-14 unbounded-system-log incident, but only ever existed as loose files on the prod host — docker-compose.yml never mounted them, so ClickHouse kept running with stock trace-level, TTL-less logging.
  • query_log/metric_log/part_log/processors_profile_log regrew to ~3.7GB over the following month (vs. ~619MB of actual business data in cp_ocpp_frames). Reconciling that backlog on merge pinned all 4 cores at ~380% CPU and OOM-crashed the container.
  • This commits the config files to the repo and mounts them in docker-compose.yml, so the fix actually takes effect and can't silently drift out of deployment again.

Remediation already applied directly on the prod host (config mounted, stale log-table backlog cleared, container healthy — CPU 380%→7%, load average 11.5→1.1). This PR is to get that fix into version control instead of living only as a manual server-side patch.

Test plan

  • Applied on prod (95.216.168.36): container healthy, CPU/mem/load back to normal after recreate
  • docker compose -f deploy/compose/docker-compose.yml up -d clickhouse on a clean checkout mounts both files without error

The zz-eveys-prod.xml / zz-eveys-async-insert.xml config (written for
the 2026-08-14 unbounded-system-log incident) existed only as loose
files on the prod host and was never referenced by docker-compose.yml,
so ClickHouse kept running with stock trace-level, TTL-less logging.
query_log/metric_log/part_log/processors_profile_log regrew to ~3.7GB
over the following month, and merging/reconciling that backlog OOM-
crashed the container, pinning all 4 cores. Commit the config files
and mount them so the fix actually takes effect and can't drift again.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant