adam/meshexplorer
1
0
Fork 0
mirror of https://github.com/ajvpot/meshexplorer.git synced 2026-07-06 01:30:58 +02:00
Code Issues Packages Projects Releases Wiki Activity

clickhouse: lift readonly read-size caps

Browse Source 
The readonly profile's max_rows_to_read / max_bytes_to_read (500MB) is exceeded by
the map/stats views, which scan the full (growing) meshcore_packets table -> the web
app failed with TOO_MANY_BYTES. Remove the read-size caps; readonly=1, allow_ddl=0,
max_memory_usage and max_execution_time remain the guardrails.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Alex Vanderpot
2026-05-29 01:48:56 -04:00
parent 7785158934
commit 6be73b04a6
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ingest/clickhouse/users.xml
+5 -2
View File
@@ -25,8 +25,11 @@
<allow_ddl>0</allow_ddl>
<max_memory_usage>10000000000</max_memory_usage>
<max_execution_time>300</max_execution_time>
<max_rows_to_read>10000000</max_rows_to_read>
<max_bytes_to_read>500000000</max_bytes_to_read>
<!-- No row/byte read caps: the map/stats views scan the full meshcore_packets
table, which grows over time. memory + execution-time limits remain the
guardrails. (0 = unlimited.) -->
<max_rows_to_read>0</max_rows_to_read>
<max_bytes_to_read>0</max_bytes_to_read>
<query_profiler_real_time_period_ns>0</query_profiler_real_time_period_ns>
<query_profiler_cpu_time_period_ns>0</query_profiler_cpu_time_period_ns>
<constraints>