1+ <?xml version =" 1.0" ?>
2+ <clickhouse >
3+ <logger >
4+ <level >information</level >
5+ <console >true</console >
6+ <log remove =" remove" />
7+ <errorlog remove =" remove" />
8+ </logger >
9+
10+ <listen_host >0.0.0.0</listen_host >
11+ <http_port >{{ .Values.clickhouse.port }}</http_port >
12+ <tcp_port >{{ .Values.clickhouse.nativePort }}</tcp_port >
13+
14+ <max_connections >4096</max_connections >
15+ <keep_alive_timeout >64</keep_alive_timeout >
16+ <max_concurrent_queries >100</max_concurrent_queries >
17+ <uncompressed_cache_size >8589934592</uncompressed_cache_size >
18+ <mark_cache_size >5368709120</mark_cache_size >
19+
20+ <path >/var/lib/clickhouse/</path >
21+ <tmp_path >/var/lib/clickhouse/tmp/</tmp_path >
22+ <user_files_path >/var/lib/clickhouse/user_files/</user_files_path >
23+
24+ <users_config >users.xml</users_config >
25+ <default_profile >default</default_profile >
26+ <default_database >default</default_database >
27+ <timezone >UTC</timezone >
28+ <mlock_executable >false</mlock_executable >
29+
30+ <!-- Query log. Used only for queries with setting log_queries = 1. -->
31+ <query_log >
32+ <database >system</database >
33+ <table >query_log</table >
34+ <flush_interval_milliseconds >7500</flush_interval_milliseconds >
35+ </query_log >
36+
37+ <!-- Metric log contains rows with current values of ProfileEvents, CurrentMetrics collected with "collect_interval_milliseconds" interval. -->
38+ <metric_log >
39+ <database >system</database >
40+ <table >metric_log</table >
41+ <flush_interval_milliseconds >7500</flush_interval_milliseconds >
42+ <collect_interval_milliseconds >1000</collect_interval_milliseconds >
43+ </metric_log >
44+
45+ <!--
46+ Asynchronous metric log contains values of metrics from
47+ system.asynchronous_metrics.
48+ -->
49+ <asynchronous_metric_log >
50+ <database >system</database >
51+ <table >asynchronous_metric_log</table >
52+ <!--
53+ Asynchronous metrics are updated once a minute, so there is
54+ no need to flush more often.
55+ -->
56+ <flush_interval_milliseconds >7000</flush_interval_milliseconds >
57+ </asynchronous_metric_log >
58+
59+ <!--
60+ OpenTelemetry log contains OpenTelemetry trace spans.
61+ -->
62+ <opentelemetry_span_log >
63+ <!--
64+ The default table creation code is insufficient, this <engine> spec
65+ is a workaround. There is no 'event_time' for this log, but two times,
66+ start and finish. It is sorted by finish time, to avoid inserting
67+ data too far away in the past (probably we can sometimes insert a span
68+ that is seconds earlier than the last span in the table, due to a race
69+ between several spans inserted in parallel). This gives the spans a
70+ global order that we can use to e.g. retry insertion into some external
71+ system.
72+ -->
73+ <engine >
74+ engine MergeTree
75+ partition by toYYYYMM(finish_date)
76+ order by (finish_date, finish_time_us, trace_id)
77+ </engine >
78+ <database >system</database >
79+ <table >opentelemetry_span_log</table >
80+ <flush_interval_milliseconds >7500</flush_interval_milliseconds >
81+ </opentelemetry_span_log >
82+
83+
84+ <!-- Crash log. Stores stack traces for fatal errors.
85+ This table is normally empty. -->
86+ <crash_log >
87+ <database >system</database >
88+ <table >crash_log</table >
89+
90+ <partition_by />
91+ <flush_interval_milliseconds >1000</flush_interval_milliseconds >
92+ </crash_log >
93+
94+ <!-- Profiling on Processors level. -->
95+ <processors_profile_log >
96+ <database >system</database >
97+ <table >processors_profile_log</table >
98+
99+ <partition_by >toYYYYMM(event_date)</partition_by >
100+ <flush_interval_milliseconds >7500</flush_interval_milliseconds >
101+ </processors_profile_log >
102+
103+ <!-- Uncomment if use part log.
104+ Part log contains information about all actions with parts in MergeTree tables (creation, deletion, merges, downloads).-->
105+ <part_log >
106+ <database >system</database >
107+ <table >part_log</table >
108+ <partition_by >toYYYYMM(event_date)</partition_by >
109+ <flush_interval_milliseconds >7500</flush_interval_milliseconds >
110+ </part_log >
111+
112+ <!-- Trace log. Stores stack traces collected by query profilers.
113+ See query_profiler_real_time_period_ns and query_profiler_cpu_time_period_ns settings. -->
114+ <trace_log >
115+ <database >system</database >
116+ <table >trace_log</table >
117+
118+ <partition_by >toYYYYMM(event_date)</partition_by >
119+ <flush_interval_milliseconds >7500</flush_interval_milliseconds >
120+ </trace_log >
121+
122+ <!-- Query thread log. Has information about all threads participated in query execution.
123+ Used only for queries with setting log_query_threads = 1. -->
124+ <query_thread_log >
125+ <database >system</database >
126+ <table >query_thread_log</table >
127+ <partition_by >toYYYYMM(event_date)</partition_by >
128+ <flush_interval_milliseconds >7500</flush_interval_milliseconds >
129+ </query_thread_log >
130+
131+ <!-- Query views log. Has information about all dependent views associated with a query.
132+ Used only for queries with setting log_query_views = 1. -->
133+ <query_views_log >
134+ <database >system</database >
135+ <table >query_views_log</table >
136+ <partition_by >toYYYYMM(event_date)</partition_by >
137+ <flush_interval_milliseconds >7500</flush_interval_milliseconds >
138+ </query_views_log >
139+
140+ <distributed_ddl >
141+ <path >/clickhouse/task_queue/ddl</path >
142+ </distributed_ddl >
143+
144+ <format_schema_path >/var/lib/clickhouse/format_schemas/</format_schema_path >
145+ </clickhouse >
0 commit comments