From 5a23146513dc41f75eacbcc25643ab015b46a0b4 Mon Sep 17 00:00:00 2001 From: unkin-agent Date: Sun, 23 Aug 2026 22:36:52 +1000 Subject: [PATCH] logging: set clickhouse readonly profile to readonly=2 (#409) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## Why The `readonly` profile used by `logreader` sets `readonly=1`, which rejects any per-query settings change. HTTP clients (logviewer, chlog) send settings params like `max_execution_time` with their queries, so every query fails with `Code: 164 DB::Exception: Cannot modify 'max_execution_time' setting in readonly mode` — logviewer healthz returns 503 and CrashLoops, chlog queries fail. `readonly=2` keeps data access read-only while permitting settings changes, which is what HTTP clients need. ## Changes - Changes the `readonly` profile in `apps/base/logging/clickhouseinstallation.yaml` from `readonly: "1"` to `readonly: "2"` Reviewed-on: https://git.unkin.net/unkin/argocd-apps/pulls/409 Co-authored-by: unkin-agent Co-committed-by: unkin-agent --- apps/base/logging/clickhouseinstallation.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/base/logging/clickhouseinstallation.yaml b/apps/base/logging/clickhouseinstallation.yaml index 08e7d9a..72641a4 100644 --- a/apps/base/logging/clickhouseinstallation.yaml +++ b/apps/base/logging/clickhouseinstallation.yaml @@ -46,7 +46,7 @@ spec: profiles: default/max_memory_usage: "10000000000" default/max_execution_time: "120" - readonly/readonly: "1" + readonly/readonly: "2" readonly/max_memory_usage: "10000000000" readonly/max_execution_time: "120" clusters: