logging: set clickhouse readonly profile to readonly=2 #409
Reference in New Issue
Block a user
Delete Branch "benvin/ch-readonly2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
The
readonlyprofile used bylogreadersetsreadonly=1, which rejects any per-query settings change. HTTP clients (logviewer, chlog) send settings params likemax_execution_timewith their queries, so every query fails withCode: 164 DB::Exception: Cannot modify 'max_execution_time' setting in readonly mode— logviewer healthz returns 503 and CrashLoops, chlog queries fail.readonly=2keeps data access read-only while permitting settings changes, which is what HTTP clients need.Changes
readonlyprofile inapps/base/logging/clickhouseinstallation.yamlfromreadonly: "1"toreadonly: "2"