devbox
小小林熬夜学编程
这个屌丝很懒，什么也没留下！
关注作者
热门标签
热门文章
当前位置:   article > 正文

ClickHouse集群搭建总结

作者：小小林熬夜学编程 | 2024-03-16 02:39:14

赞

踩

clickhouse集群搭建

简介

 

ClickHouse是俄罗斯最大的搜素引擎Yandex于2016年开源的列式数据库管理系统，使用C++ 语言编写, 主要应用于OLAP场景。

使用理由
在大数据量的情况下，能以很低的延迟返回查询结果。

笔者注： 在单机亿级数据量的场景下可以达到毫秒级的查询性能，单机能处理百亿的数据量， 聚合、计数、求和等统计操作的性能是MySQL的100倍。


主要特点

  1. 列式储存
  2. 数据压缩
  3. 支持大部分标准sql
  4. 支持分区（类似分表）
  5. 使用稀疏索引作为索引的主要实现
  6. 支持分布式
  7. 可以在牺牲精度的前提下，快速的返回一个近似结果

缺点

  1. 没有完整的事务支持。
  2. 缺少高频率，低延迟的修改或删除已存在数据的能力。
  3. 稀疏索引使得ClickHouse不适合通过其键检索单行的点查询。
  4. 没有自增类型

来源：ClickHouse使用总结_推迟享受。的博客-CSDN博客

ClickHouse集群架构

ClickHouse分片

定义
ClickHouse中的每个服务节点都可称为一个shard(分片)。
Distributed表引擎自身不存储任何数据，它能够作为分布式表的一层透明代理，在集群内部自动开展数据的写入、分发、查询、路由等工作。

zk作用

Zookeeper 安装3节点，版本要求在 ZooKeeper 3.4.5 或更高版本.

你可以配置任何现有的 ZooKeeper 集群，系统会使用里面的目录来存取元数据（该目录在创建可复制表时指定）。

如果配置文件中没有设置 ZooKeeper ，则无法创建复制表，并且任何现有的复制表都将变为只读。

在 ClickHouse 中，ZooKeeper 不参与任何实质性的数据传输。ZooKeeper 在 ClickHouse 中主要用在副本表数据的同步(ReplicatedMergeTree引擎)以及分布式表(Distributed)的操作上。因此需要确保zk集群的硬盘空间和高可用。


查看zk配置是否生效

如果 Zookeeper 配置成功，可以查看 system.zookeeper 这张表，如果存在则表示配置成功，不存在请检查各节点关于 Zookeeper 的配置，同时也可以利用该表查看 Zookeeper 中的元数据信息

select * from system.zookeeper where path='/';

 docker搭建ck集群

系统准备


#关闭firewall 与 selinux 和 swap
systemctl disabled firewalled && systemctl stop firewalled
setenforce 0
sed -ri 's#(^SELINUX=).*#\1disabled#g' /etc/selinux/config
swapoff -a
sed -ri 's/.*swap.*/#&/' /etc/fstab

搭建zk集群

Zookeeper 安装3节点，版本要求在 ZooKeeper 3.4.5 或更高版本.

在每个服务器上你想存放的位置，新建一个文件夹来存放zk的配置信息，这里是 /usr/soft/zookeeper/ ，在每个服务器上依次运行以下启动命令：

server01执行：

暴露出的使用端口是2181端口，集群通信端口是2888和3888端口。

docker run -d  --name zookeeper_node --restart always \
-v /usr/soft/zookeeper/data:/data \
-v /usr/soft/zookeeper/datalog:/datalog \
-v /usr/soft/zookeeper/logs:/logs \
-v /usr/soft/zookeeper/conf:/conf \
--network host  \
-e ZOO_MY_ID=1  zookeeper

server02执行：

docker run -d   --name zookeeper_node --restart always \
-v /usr/soft/zookeeper/data:/data \
-v /usr/soft/zookeeper/datalog:/datalog \
-v /usr/soft/zookeeper/logs:/logs \
-v /usr/soft/zookeeper/conf:/conf \
--network host  \
-e ZOO_MY_ID=2  zookeeper

server03执行：

docker run -d  --name zookeeper_node --restart always \
-v /usr/soft/zookeeper/data:/data \
-v /usr/soft/zookeeper/datalog:/datalog \
-v /usr/soft/zookeeper/logs:/logs \
-v /usr/soft/zookeeper/conf:/conf \
--network host  \
-e ZOO_MY_ID=3  zookeeper

创建目录


创建ClickHouse的工作目录，每个节点都要创建：

mkdir -p /data/clickhouse/data
mkdir -p /data/clickhouse/logs
mkdir -p /data/clickhouse/conf


配置文件


1.config.xml


在每个节点 /data/clickhouse/conf 目录下放入文件：config.xml，注意检查端口，避免冲突。

  1. <?xml version="1.0"?>
  2. <!--
  3.   NOTE: User and query level settings are set up in "users.xml" file.
  4.   If you have accidentally specified user-level settings here, server won't start.
  5.   You can either move the settings to the right place inside "users.xml" file
  6.    or add <skip_check_for_incorrect_settings>1</skip_check_for_incorrect_settings> here.
  7. -->
  8. <clickhouse>
  9.     <logger>
  10.         <!-- Possible levels [1]:
  12.           - none (turns off logging)
  13.           - fatal
  14.           - critical
  15.           - error
  16.           - warning
  17.           - notice
  18.           - information
  19.           - debug
  20.           - trace
  21.           - test (not for production usage)
  23.             [1]: https://github.com/pocoproject/poco/blob/poco-1.9.4-release/Foundation/include/Poco/Logger.h#L105-L114
  24.         -->
  25.         <level>trace</level>
  26.         <log>/var/log/clickhouse-server/clickhouse-server.log</log>
  27.         <errorlog>/var/log/clickhouse-server/clickhouse-server.err.log</errorlog>
  28.         <!-- Rotation policy
  29.              See https://github.com/pocoproject/poco/blob/poco-1.9.4-release/Foundation/include/Poco/FileChannel.h#L54-L85
  30.           -->
  31.         <size>1000M</size>
  32.         <count>10</count>
  33.         <!-- <console>1</console> --> <!-- Default behavior is autodetection (log to console if not daemon mode and is tty) -->
  34.  
  35.         <!-- Per level overrides (legacy):
  37.         For example to suppress logging of the ConfigReloader you can use:
  38.         NOTE: levels.logger is reserved, see below.
  39.         -->
  40.         <!--
  41.         <levels>
  42.           <ConfigReloader>none</ConfigReloader>
  43.         </levels>
  44.         -->
  45.  
  46.         <!-- Per level overrides:
  48.         For example to suppress logging of the RBAC for default user you can use:
  49.         (But please note that the logger name maybe changed from version to version, even after minor upgrade)
  50.         -->
  51.         <!--
  52.         <levels>
  53.           <logger>
  54.             <name>ContextAccess (default)</name>
  55.             <level>none</level>
  56.           </logger>
  57.           <logger>
  58.             <name>DatabaseOrdinary (test)</name>
  59.             <level>none</level>
  60.           </logger>
  61.         </levels>
  62.         -->
  63.     </logger>
  64.  
  65.     <!-- Add headers to response in options request. OPTIONS method is used in CORS preflight requests. -->
  66.     <!-- It is off by default. Next headers are obligate for CORS.-->
  67.     <!-- http_options_response>
  68.         <header>
  69.             <name>Access-Control-Allow-Origin</name>
  70.             <value>*</value>
  71.         </header>
  72.         <header>
  73.             <name>Access-Control-Allow-Headers</name>
  74.             <value>origin, x-requested-with</value>
  75.         </header>
  76.         <header>
  77.             <name>Access-Control-Allow-Methods</name>
  78.             <value>POST, GET, OPTIONS</value>
  79.         </header>
  80.         <header>
  81.             <name>Access-Control-Max-Age</name>
  82.             <value>86400</value>
  83.         </header>
  84.     </http_options_response -->
  85.  
  86.     <!-- It is the name that will be shown in the clickhouse-client.
  87.          By default, anything with "production" will be highlighted in red in query prompt.
  88.     -->
  89.     <!--display_name>production</display_name-->
  90.  
  91.     <!-- Port for HTTP API. See also 'https_port' for secure connections.
  92.          This interface is also used by ODBC and JDBC drivers (DataGrip, Dbeaver, ...)
  93.          and by most of web interfaces (embedded UI, Grafana, Redash, ...).
  94.       -->
  95.     <http_port>8123</http_port>
  96.  
  97.     <!-- Port for interaction by native protocol with:
  98.          - clickhouse-client and other native ClickHouse tools (clickhouse-benchmark, clickhouse-copier);
  99.          - clickhouse-server with other clickhouse-servers for distributed query processing;
  100.          - ClickHouse drivers and applications supporting native protocol
  101.          (this protocol is also informally called as "the TCP protocol");
  102.          See also 'tcp_port_secure' for secure connections.
  103.     -->
  104.     <tcp_port>10000</tcp_port>
  105.  
  106.     <!-- Compatibility with MySQL protocol.
  107.          ClickHouse will pretend to be MySQL for applications connecting to this port.
  108.     -->
  109.     <mysql_port>9004</mysql_port>
  110.  
  111.     <!-- Compatibility with PostgreSQL protocol.
  112.          ClickHouse will pretend to be PostgreSQL for applications connecting to this port.
  113.     -->
  114.     <postgresql_port>9005</postgresql_port>
  115.  
  116.     <!-- HTTP API with TLS (HTTPS).
  117.          You have to configure certificate to enable this interface.
  118.          See the openSSL section below.
  119.     -->
  120.     <!-- <https_port>8443</https_port> -->
  121.  
  122.     <!-- Native interface with TLS.
  123.          You have to configure certificate to enable this interface.
  124.          See the openSSL section below.
  125.     -->
  126.     <!-- <tcp_port_secure>9440</tcp_port_secure> -->
  127.  
  128.     <!-- Native interface wrapped with PROXYv1 protocol
  129.          PROXYv1 header sent for every connection.
  130.          ClickHouse will extract information about proxy-forwarded client address from the header.
  131.     -->
  132.     <!-- <tcp_with_proxy_port>9011</tcp_with_proxy_port> -->
  133.  
  134.     <!-- Port for communication between replicas. Used for data exchange.
  135.          It provides low-level data access between servers.
  136.          This port should not be accessible from untrusted networks.
  137.          See also 'interserver_http_credentials'.
  138.          Data transferred over connections to this port should not go through untrusted networks.
  139.          See also 'interserver_https_port'.
  140.       -->
  141.     <interserver_http_port>9009</interserver_http_port>
  142.  
  143.     <!-- Port for communication between replicas with TLS.
  144.          You have to configure certificate to enable this interface.
  145.          See the openSSL section below.
  146.          See also 'interserver_http_credentials'.
  147.       -->
  148.     <!-- <interserver_https_port>9010</interserver_https_port> -->
  149.  
  150.     <!-- Hostname that is used by other replicas to request this server.
  151.          If not specified, then it is determined analogous to 'hostname -f' command.
  152.          This setting could be used to switch replication to another network interface
  153.          (the server may be connected to multiple networks via multiple addresses)
  154.       -->
  155.  
  156.     <!--
  157.     <interserver_http_host>example.clickhouse.com</interserver_http_host>
  158.     -->
  159.  
  160.     <!-- You can specify credentials for authenthication between replicas.
  161.          This is required when interserver_https_port is accessible from untrusted networks,
  162.          and also recommended to avoid SSRF attacks from possibly compromised services in your network.
  163.       -->
  164.     <!--<interserver_http_credentials>
  165.         <user>interserver</user>
  166.         <password></password>
  167.     </interserver_http_credentials>-->
  168.  
  169.     <!-- Listen specified address.
  170.          Use :: (wildcard IPv6 address), if you want to accept connections both with IPv4 and IPv6 from everywhere.
  171.          Notes:
  172.          If you open connections from wildcard address, make sure that at least one of the following measures applied:
  173.          - server is protected by firewall and not accessible from untrusted networks;
  174.          - all users are restricted to subset of network addresses (see users.xml);
  175.          - all users have strong passwords, only secure (TLS) interfaces are accessible, or connections are only made via TLS interfaces.
  176.          - users without password have readonly access.
  177.          See also: https://www.shodan.io/search?query=clickhouse
  178.       -->
  179.     <!-- <listen_host>::</listen_host> -->
  180.  
  181.  
  182.     <!-- Same for hosts without support for IPv6: -->
  183.     <listen_host>0.0.0.0</listen_host>
  184.  
  185.     <!-- Default values - try listen localhost on IPv4 and IPv6. -->
  186.     <!--
  187.     <listen_host>::1</listen_host>
  188.     <listen_host>127.0.0.1</listen_host>
  189.     -->
  190.  
  191.     <!-- Don't exit if IPv6 or IPv4 networks are unavailable while trying to listen. -->
  192.     <!-- <listen_try>0</listen_try> -->
  193.  
  194.     <!-- Allow multiple servers to listen on the same address:port. This is not recommended.
  195.       -->
  196.     <!-- <listen_reuse_port>0</listen_reuse_port> -->
  197.  
  198.     <!-- <listen_backlog>4096</listen_backlog> -->
  199.  
  200.     <max_connections>4096</max_connections>
  201.  
  202.     <!-- For 'Connection: keep-alive' in HTTP 1.1 -->
  203.     <keep_alive_timeout>3</keep_alive_timeout>
  204.  
  205.     <!-- gRPC protocol (see src/Server/grpc_protos/clickhouse_grpc.proto for the API) -->
  206.     <!-- <grpc_port>9100</grpc_port> -->
  207.     <grpc>
  208.         <enable_ssl>false</enable_ssl>
  209.  
  210.         <!-- The following two files are used only if enable_ssl=1 -->
  211.         <ssl_cert_file>/path/to/ssl_cert_file</ssl_cert_file>
  212.         <ssl_key_file>/path/to/ssl_key_file</ssl_key_file>
  213.  
  214.         <!-- Whether server will request client for a certificate -->
  215.         <ssl_require_client_auth>false</ssl_require_client_auth>
  216.  
  217.         <!-- The following file is used only if ssl_require_client_auth=1 -->
  218.         <ssl_ca_cert_file>/path/to/ssl_ca_cert_file</ssl_ca_cert_file>
  219.  
  220.         <!-- Default transport compression type (can be overridden by client, see the transport_compression_type field in QueryInfo).
  221.              Supported algorithms: none, deflate, gzip, stream_gzip -->
  222.         <transport_compression_type>none</transport_compression_type>
  223.  
  224.         <!-- Default transport compression level. Supported levels: 0..3 -->
  225.         <transport_compression_level>0</transport_compression_level>
  226.  
  227.         <!-- Send/receive message size limits in bytes. -1 means unlimited -->
  228.         <max_send_message_size>-1</max_send_message_size>
  229.         <max_receive_message_size>-1</max_receive_message_size>
  230.  
  231.         <!-- Enable if you want very detailed logs -->
  232.         <verbose_logs>false</verbose_logs>
  233.     </grpc>
  234.  
  235.     <!-- Used with https_port and tcp_port_secure. Full ssl options list: https://github.com/ClickHouse-Extras/poco/blob/master/NetSSL_OpenSSL/include/Poco/Net/SSLManager.h#L71 -->
  236.     <openSSL>
  237.         <server> <!-- Used for https server AND secure tcp port -->
  238.             <!-- openssl req -subj "/CN=localhost" -new -newkey rsa:2048 -days 365 -nodes -x509 -keyout /etc/clickhouse-server/server.key -out /etc/clickhouse-server/server.crt -->
  239.             <!-- <certificateFile>/etc/clickhouse-server/server.crt</certificateFile>
  240.             <privateKeyFile>/etc/clickhouse-server/server.key</privateKeyFile> -->
  241.             <!-- dhparams are optional. You can delete the <dhParamsFile> element.
  242.                  To generate dhparams, use the following command:
  243.                   openssl dhparam -out /etc/clickhouse-server/dhparam.pem 4096
  244.                  Only file format with BEGIN DH PARAMETERS is supported.
  245.               -->
  246.             <!-- <dhParamsFile>/etc/clickhouse-server/dhparam.pem</dhParamsFile>-->
  247.             <verificationMode>none</verificationMode>
  248.             <loadDefaultCAFile>true</loadDefaultCAFile>
  249.             <cacheSessions>true</cacheSessions>
  250.             <disableProtocols>sslv2,sslv3</disableProtocols>
  251.             <preferServerCiphers>true</preferServerCiphers>
  252.         </server>
  253.  
  254.         <client> <!-- Used for connecting to https dictionary source and secured Zookeeper communication -->
  255.             <loadDefaultCAFile>true</loadDefaultCAFile>
  256.             <cacheSessions>true</cacheSessions>
  257.             <disableProtocols>sslv2,sslv3</disableProtocols>
  258.             <preferServerCiphers>true</preferServerCiphers>
  259.             <!-- Use for self-signed: <verificationMode>none</verificationMode> -->
  260.             <invalidCertificateHandler>
  261.                 <!-- Use for self-signed: <name>AcceptCertificateHandler</name> -->
  262.                 <name>RejectCertificateHandler</name>
  263.             </invalidCertificateHandler>
  264.         </client>
  265.     </openSSL>
  266.  
  267.     <!-- Default root page on http[s] server. For example load UI from https://tabix.io/ when opening http://localhost:8123 -->
  268.     <!--
  269.     <http_server_default_response><![CDATA[<html ng-app="SMI2"><head><base href="http://ui.tabix.io/"></head><body><div ui-view="" class="content-ui"></div><script src="http://loader.tabix.io/master.js"></script></body></html>]]></http_server_default_response>
  270.     -->
  271.  
  272.     <!-- Maximum number of concurrent queries. -->
  273.     <max_concurrent_queries>100</max_concurrent_queries>
  274.  
  275.     <!-- Maximum memory usage (resident set size) for server process.
  276.          Zero value or unset means default. Default is "max_server_memory_usage_to_ram_ratio" of available physical RAM.
  277.          If the value is larger than "max_server_memory_usage_to_ram_ratio" of available physical RAM, it will be cut down.
  279.          The constraint is checked on query execution time.
  280.          If a query tries to allocate memory and the current memory usage plus allocation is greater
  281.           than specified threshold, exception will be thrown.
  283.          It is not practical to set this constraint to small values like just a few gigabytes,
  284.           because memory allocator will keep this amount of memory in caches and the server will deny service of queries.
  285.       -->
  286.     <max_server_memory_usage>0</max_server_memory_usage>
  287.  
  288.     <!-- Maximum number of threads in the Global thread pool.
  289.     This will default to a maximum of 10000 threads if not specified.
  290.     This setting will be useful in scenarios where there are a large number
  291.     of distributed queries that are running concurrently but are idling most
  292.     of the time, in which case a higher number of threads might be required.
  293.     -->
  294.  
  295.     <max_thread_pool_size>10000</max_thread_pool_size>
  296.  
  297.     <!-- Number of workers to recycle connections in background (see also drain_timeout).
  298.          If the pool is full, connection will be drained synchronously. -->
  299.     <!-- <max_threads_for_connection_collector>10</max_threads_for_connection_collector> -->
  300.  
  301.     <!-- On memory constrained environments you may have to set this to value larger than 1.
  302.       -->
  303.     <max_server_memory_usage_to_ram_ratio>0.9</max_server_memory_usage_to_ram_ratio>
  304.  
  305.     <!-- Simple server-wide memory profiler. Collect a stack trace at every peak allocation step (in bytes).
  306.          Data will be stored in system.trace_log table with query_id = empty string.
  307.          Zero means disabled.
  308.       -->
  309.     <total_memory_profiler_step>4194304</total_memory_profiler_step>
  310.  
  311.     <!-- Collect random allocations and deallocations and write them into system.trace_log with 'MemorySample' trace_type.
  312.          The probability is for every alloc/free regardless to the size of the allocation.
  313.          Note that sampling happens only when the amount of untracked memory exceeds the untracked memory limit,
  314.           which is 4 MiB by default but can be lowered if 'total_memory_profiler_step' is lowered.
  315.          You may want to set 'total_memory_profiler_step' to 1 for extra fine grained sampling.
  316.       -->
  317.     <total_memory_tracker_sample_probability>0</total_memory_tracker_sample_probability>
  318.  
  319.     <!-- Set limit on number of open files (default: maximum). This setting makes sense on Mac OS X because getrlimit() fails to retrieve
  320.          correct maximum value. -->
  321.     <!-- <max_open_files>262144</max_open_files> -->
  322.  
  323.     <!-- Size of cache of uncompressed blocks of data, used in tables of MergeTree family.
  324.          In bytes. Cache is single for server. Memory is allocated only on demand.
  325.          Cache is used when 'use_uncompressed_cache' user setting turned on (off by default).
  326.          Uncompressed cache is advantageous only for very short queries and in rare cases.
  328.          Note: uncompressed cache can be pointless for lz4, because memory bandwidth
  329.          is slower than multi-core decompression on some server configurations.
  330.          Enabling it can sometimes paradoxically make queries slower.
  331.       -->
  332.     <uncompressed_cache_size>8589934592</uncompressed_cache_size>
  333.  
  334.     <!-- Approximate size of mark cache, used in tables of MergeTree family.
  335.          In bytes. Cache is single for server. Memory is allocated only on demand.
  336.          You should not lower this value.
  337.       -->
  338.     <mark_cache_size>5368709120</mark_cache_size>
  339.  
  340.  
  341.     <!-- If you enable the `min_bytes_to_use_mmap_io` setting,
  342.          the data in MergeTree tables can be read with mmap to avoid copying from kernel to userspace.
  343.          It makes sense only for large files and helps only if data reside in page cache.
  344.          To avoid frequent open/mmap/munmap/close calls (which are very expensive due to consequent page faults)
  345.          and to reuse mappings from several threads and queries,
  346.          the cache of mapped files is maintained. Its size is the number of mapped regions (usually equal to the number of mapped files).
  347.          The amount of data in mapped files can be monitored
  348.          in system.metrics, system.metric_log by the MMappedFiles, MMappedFileBytes metrics
  349.          and in system.asynchronous_metrics, system.asynchronous_metrics_log by the MMapCacheCells metric,
  350.          and also in system.events, system.processes, system.query_log, system.query_thread_log, system.query_views_log by the
  351.          CreatedReadBufferMMap, CreatedReadBufferMMapFailed, MMappedFileCacheHits, MMappedFileCacheMisses events.
  352.          Note that the amount of data in mapped files does not consume memory directly and is not accounted
  353.          in query or server memory usage - because this memory can be discarded similar to OS page cache.
  354.          The cache is dropped (the files are closed) automatically on removal of old parts in MergeTree,
  355.          also it can be dropped manually by the SYSTEM DROP MMAP CACHE query.
  356.       -->
  357.     <mmap_cache_size>1000</mmap_cache_size>
  358.  
  359.     <!-- Cache size in bytes for compiled expressions.-->
  360.     <compiled_expression_cache_size>134217728</compiled_expression_cache_size>
  361.  
  362.     <!-- Cache size in elements for compiled expressions.-->
  363.     <compiled_expression_cache_elements_size>10000</compiled_expression_cache_elements_size>
  364.  
  365.     <!-- Path to data directory, with trailing slash. -->
  366.     <path>/var/lib/clickhouse/</path>
  367.  
  368.     <!-- Multi-disk configuration example: -->
  369.     <!--
  370.     <storage_configuration>
  371.         <disks>
  372.             <default>
  373.                 <keep_free_space_bytes>0</keep_free_space_bytes>
  374.             </default>
  375.             <data>
  376.                 <path>/data/</path>
  377.                 <keep_free_space_bytes>0</keep_free_space_bytes>
  378.             </data>
  379.             <s3>
  380.                 <type>s3</type>
  381.                 <endpoint>http://path/to/endpoint</endpoint>
  382.                 <access_key_id>your_access_key_id</access_key_id>
  383.                 <secret_access_key>your_secret_access_key</secret_access_key>
  384.             </s3>
  385.             <blob_storage_disk>
  386.                 <type>azure_blob_storage</type>
  387.                 <storage_account_url>http://account.blob.core.windows.net</storage_account_url>
  388.                 <container_name>container</container_name>
  389.                 <account_name>account</account_name>
  390.                 <account_key>pass123</account_key>
  391.                 <metadata_path>/var/lib/clickhouse/disks/blob_storage_disk/</metadata_path>
  392.                 <cache_enabled>true</cache_enabled>
  393.                 <cache_path>/var/lib/clickhouse/disks/blob_storage_disk/cache/</cache_path>
  394.                 <skip_access_check>false</skip_access_check>
  395.             </blob_storage_disk>
  396.         </disks>
  398.         <policies>
  399.             <all>
  400.                 <volumes>
  401.                     <main>
  402.                         <disk>default</disk>
  403.                         <disk>data</disk>
  404.                         <disk>s3</disk>
  405.                         <disk>blob_storage_disk</disk>
  407.                         <max_data_part_size_bytes></max_data_part_size_bytes>
  408.                         <max_data_part_size_ratio></max_data_part_size_ratio>
  409.                         <perform_ttl_move_on_insert>true</perform_ttl_move_on_insert>
  410.                         <prefer_not_to_merge>false</prefer_not_to_merge>
  411.                         <load_balancing>round_robin</load_balancing>
  412.                     </main>
  413.                 </volumes>
  414.                 <move_factor>0.2</move_factor>
  415.             </all>
  416.         </policies>
  417.     </storage_configuration>
  418.     -->
  419.  
  420.  
  421.     <!-- Path to temporary data for processing hard queries. -->
  422.     <tmp_path>/var/lib/clickhouse/tmp/</tmp_path>
  423.  
  424.     <!-- Disable AuthType plaintext_password and no_password for ACL. -->
  425.     <!-- <allow_plaintext_password>0</allow_plaintext_password> -->
  426.     <!-- <allow_no_password>0</allow_no_password> -->`
  427.  
  428.     <!-- Policy from the <storage_configuration> for the temporary files.
  429.          If not set <tmp_path> is used, otherwise <tmp_path> is ignored.
  431.          Notes:
  432.          - move_factor              is ignored
  433.          - keep_free_space_bytes    is ignored
  434.          - max_data_part_size_bytes is ignored
  435.          - you must have exactly one volume in that policy
  436.     -->
  437.     <!-- <tmp_policy>tmp</tmp_policy> -->
  438.  
  439.     <!-- Directory with user provided files that are accessible by 'file' table function. -->
  440.     <user_files_path>/var/lib/clickhouse/user_files/</user_files_path>
  441.  
  442.     <!-- LDAP server definitions. -->
  443.     <ldap_servers>
  444.         <!-- List LDAP servers with their connection parameters here to later 1) use them as authenticators for dedicated local users,
  445.               who have 'ldap' authentication mechanism specified instead of 'password', or to 2) use them as remote user directories.
  446.              Parameters:
  447.                 host - LDAP server hostname or IP, this parameter is mandatory and cannot be empty.
  448.                 port - LDAP server port, default is 636 if enable_tls is set to true, 389 otherwise.
  449.                 bind_dn - template used to construct the DN to bind to.
  450.                         The resulting DN will be constructed by replacing all '{user_name}' substrings of the template with the actual
  451.                          user name during each authentication attempt.
  452.                 user_dn_detection - section with LDAP search parameters for detecting the actual user DN of the bound user.
  453.                         This is mainly used in search filters for further role mapping when the server is Active Directory. The
  454.                          resulting user DN will be used when replacing '{user_dn}' substrings wherever they are allowed. By default,
  455.                          user DN is set equal to bind DN, but once search is performed, it will be updated with to the actual detected
  456.                          user DN value.
  457.                     base_dn - template used to construct the base DN for the LDAP search.
  458.                             The resulting DN will be constructed by replacing all '{user_name}' and '{bind_dn}' substrings
  459.                              of the template with the actual user name and bind DN during the LDAP search.
  460.                     scope - scope of the LDAP search.
  461.                             Accepted values are: 'base', 'one_level', 'children', 'subtree' (the default).
  462.                     search_filter - template used to construct the search filter for the LDAP search.
  463.                             The resulting filter will be constructed by replacing all '{user_name}', '{bind_dn}', and '{base_dn}'
  464.                              substrings of the template with the actual user name, bind DN, and base DN during the LDAP search.
  465.                             Note, that the special characters must be escaped properly in XML.
  466.                 verification_cooldown - a period of time, in seconds, after a successful bind attempt, during which a user will be assumed
  467.                          to be successfully authenticated for all consecutive requests without contacting the LDAP server.
  468.                         Specify 0 (the default) to disable caching and force contacting the LDAP server for each authentication request.
  469.                 enable_tls - flag to trigger use of secure connection to the LDAP server.
  470.                         Specify 'no' for plain text (ldap://) protocol (not recommended).
  471.                         Specify 'yes' for LDAP over SSL/TLS (ldaps://) protocol (recommended, the default).
  472.                         Specify 'starttls' for legacy StartTLS protocol (plain text (ldap://) protocol, upgraded to TLS).
  473.                 tls_minimum_protocol_version - the minimum protocol version of SSL/TLS.
  474.                         Accepted values are: 'ssl2', 'ssl3', 'tls1.0', 'tls1.1', 'tls1.2' (the default).
  475.                 tls_require_cert - SSL/TLS peer certificate verification behavior.
  476.                         Accepted values are: 'never', 'allow', 'try', 'demand' (the default).
  477.                 tls_cert_file - path to certificate file.
  478.                 tls_key_file - path to certificate key file.
  479.                 tls_ca_cert_file - path to CA certificate file.
  480.                 tls_ca_cert_dir - path to the directory containing CA certificates.
  481.                 tls_cipher_suite - allowed cipher suite (in OpenSSL notation).
  482.              Example:
  483.                 <my_ldap_server>
  484.                     <host>localhost</host>
  485.                     <port>636</port>
  486.                     <bind_dn>uid={user_name},ou=users,dc=example,dc=com</bind_dn>
  487.                     <verification_cooldown>300</verification_cooldown>
  488.                     <enable_tls>yes</enable_tls>
  489.                     <tls_minimum_protocol_version>tls1.2</tls_minimum_protocol_version>
  490.                     <tls_require_cert>demand</tls_require_cert>
  491.                     <tls_cert_file>/path/to/tls_cert_file</tls_cert_file>
  492.                     <tls_key_file>/path/to/tls_key_file</tls_key_file>
  493.                     <tls_ca_cert_file>/path/to/tls_ca_cert_file</tls_ca_cert_file>
  494.                     <tls_ca_cert_dir>/path/to/tls_ca_cert_dir</tls_ca_cert_dir>
  495.                     <tls_cipher_suite>ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:AES256-GCM-SHA384</tls_cipher_suite>
  496.                 </my_ldap_server>
  497.              Example (typical Active Directory with configured user DN detection for further role mapping):
  498.                 <my_ad_server>
  499.                     <host>localhost</host>
  500.                     <port>389</port>
  501.                     <bind_dn>EXAMPLE\{user_name}</bind_dn>
  502.                     <user_dn_detection>
  503.                         <base_dn>CN=Users,DC=example,DC=com</base_dn>
  504.                         <search_filter>(&(objectClass=user)(sAMAccountName={user_name}))</search_filter>
  505.                     </user_dn_detection>
  506.                     <enable_tls>no</enable_tls>
  507.                 </my_ad_server>
  508.         -->
  509.     </ldap_servers>
  510.  
  511.     <!-- To enable Kerberos authentication support for HTTP requests (GSS-SPNEGO), for those users who are explicitly configured
  512.           to authenticate via Kerberos, define a single 'kerberos' section here.
  513.          Parameters:
  514.             principal - canonical service principal name, that will be acquired and used when accepting security contexts.
  515.                     This parameter is optional, if omitted, the default principal will be used.
  516.                     This parameter cannot be specified together with 'realm' parameter.
  517.             realm - a realm, that will be used to restrict authentication to only those requests whose initiator's realm matches it.
  518.                     This parameter is optional, if omitted, no additional filtering by realm will be applied.
  519.                     This parameter cannot be specified together with 'principal' parameter.
  520.          Example:
  521.             <kerberos />
  522.          Example:
  523.             <kerberos>
  524.                 <principal>HTTP/clickhouse.example.com@EXAMPLE.COM</principal>
  525.             </kerberos>
  526.          Example:
  527.             <kerberos>
  528.                 <realm>EXAMPLE.COM</realm>
  529.             </kerberos>
  530.     -->
  531.  
  532.     <!-- Sources to read users, roles, access rights, profiles of settings, quotas. -->
  533.     <user_directories>
  534.         <users_xml>
  535.             <!-- Path to configuration file with predefined users. -->
  536.             <path>users.xml</path>
  537.         </users_xml>
  538.         <local_directory>
  539.             <!-- Path to folder where users created by SQL commands are stored. -->
  540.             <path>/var/lib/clickhouse/access/</path>
  541.         </local_directory>
  542.  
  543.         <!-- To add an LDAP server as a remote user directory of users that are not defined locally, define a single 'ldap' section
  544.               with the following parameters:
  545.                 server - one of LDAP server names defined in 'ldap_servers' config section above.
  546.                         This parameter is mandatory and cannot be empty.
  547.                 roles - section with a list of locally defined roles that will be assigned to each user retrieved from the LDAP server.
  548.                         If no roles are specified here or assigned during role mapping (below), user will not be able to perform any
  549.                          actions after authentication.
  550.                 role_mapping - section with LDAP search parameters and mapping rules.
  551.                         When a user authenticates, while still bound to LDAP, an LDAP search is performed using search_filter and the
  552.                          name of the logged in user. For each entry found during that search, the value of the specified attribute is
  553.                          extracted. For each attribute value that has the specified prefix, the prefix is removed, and the rest of the
  554.                          value becomes the name of a local role defined in ClickHouse, which is expected to be created beforehand by
  555.                          CREATE ROLE command.
  556.                         There can be multiple 'role_mapping' sections defined inside the same 'ldap' section. All of them will be
  557.                          applied.
  558.                     base_dn - template used to construct the base DN for the LDAP search.
  559.                             The resulting DN will be constructed by replacing all '{user_name}', '{bind_dn}', and '{user_dn}'
  560.                              substrings of the template with the actual user name, bind DN, and user DN during each LDAP search.
  561.                     scope - scope of the LDAP search.
  562.                             Accepted values are: 'base', 'one_level', 'children', 'subtree' (the default).
  563.                     search_filter - template used to construct the search filter for the LDAP search.
  564.                             The resulting filter will be constructed by replacing all '{user_name}', '{bind_dn}', '{user_dn}', and
  565.                              '{base_dn}' substrings of the template with the actual user name, bind DN, user DN, and base DN during
  566.                              each LDAP search.
  567.                             Note, that the special characters must be escaped properly in XML.
  568.                     attribute - attribute name whose values will be returned by the LDAP search. 'cn', by default.
  569.                     prefix - prefix, that will be expected to be in front of each string in the original list of strings returned by
  570.                              the LDAP search. Prefix will be removed from the original strings and resulting strings will be treated
  571.                              as local role names. Empty, by default.
  572.              Example:
  573.                 <ldap>
  574.                     <server>my_ldap_server</server>
  575.                     <roles>
  576.                         <my_local_role1 />
  577.                         <my_local_role2 />
  578.                     </roles>
  579.                     <role_mapping>
  580.                         <base_dn>ou=groups,dc=example,dc=com</base_dn>
  581.                         <scope>subtree</scope>
  582.                         <search_filter>(&(objectClass=groupOfNames)(member={bind_dn}))</search_filter>
  583.                         <attribute>cn</attribute>
  584.                         <prefix>clickhouse_</prefix>
  585.                     </role_mapping>
  586.                 </ldap>
  587.              Example (typical Active Directory with role mapping that relies on the detected user DN):
  588.                 <ldap>
  589.                     <server>my_ad_server</server>
  590.                     <role_mapping>
  591.                         <base_dn>CN=Users,DC=example,DC=com</base_dn>
  592.                         <attribute>CN</attribute>
  593.                         <scope>subtree</scope>
  594.                         <search_filter>(&(objectClass=group)(member={user_dn}))</search_filter>
  595.                         <prefix>clickhouse_</prefix>
  596.                     </role_mapping>
  597.                 </ldap>
  598.         -->
  599.     </user_directories>
  600.  
  601.     <access_control_improvements>
  602.         <!-- Enables logic that users without permissive row policies can still read rows using a SELECT query.
  603.              For example, if there two users A, B and a row policy is defined only for A, then
  604.              if this setting is true the user B will see all rows, and if this setting is false the user B will see no rows.
  605.              By default this setting is false for compatibility with earlier access configurations. -->
  606.         <users_without_row_policies_can_read_rows>false</users_without_row_policies_can_read_rows>
  607.  
  608.         <!-- By default, for backward compatibility ON CLUSTER queries ignore CLUSTER grant,
  609.              however you can change this behaviour by setting this to true -->
  610.         <on_cluster_queries_require_cluster_grant>false</on_cluster_queries_require_cluster_grant>
  611.  
  612.         <!-- By default, for backward compatibility "SELECT * FROM system.<table>" doesn't require any grants and can be executed
  613.              by any user. You can change this behaviour by setting this to true.
  614.              If it's set to true then this query requires "GRANT SELECT ON system.<table>" just like as for non-system tables.
  615.              Exceptions: a few system tables ("tables", "columns", "databases", and some constant tables like "one", "contributors")
  616.              are still accessible for everyone; and if there is a SHOW privilege (e.g. "SHOW USERS") granted the corresponding system
  617.              table (i.e. "system.users") will be accessible. -->
  618.         <select_from_system_db_requires_grant>false</select_from_system_db_requires_grant>
  619.  
  620.         <!-- By default, for backward compatibility "SELECT * FROM information_schema.<table>" doesn't require any grants and can be
  621.              executed by any user. You can change this behaviour by setting this to true.
  622.              If it's set to true then this query requires "GRANT SELECT ON information_schema.<table>" just like as for ordinary tables. -->
  623.         <select_from_information_schema_requires_grant>false</select_from_information_schema_requires_grant>
  624.     </access_control_improvements>
  625.  
  626.     <!-- Default profile of settings. -->
  627.     <default_profile>default</default_profile>
  628.  
  629.     <!-- Comma-separated list of prefixes for user-defined settings. -->
  630.     <custom_settings_prefixes></custom_settings_prefixes>
  631.  
  632.     <!-- System profile of settings. This settings are used by internal processes (Distributed DDL worker and so on). -->
  633.     <!-- <system_profile>default</system_profile> -->
  634.  
  635.     <!-- Buffer profile of settings.
  636.          This settings are used by Buffer storage to flush data to the underlying table.
  637.          Default: used from system_profile directive.
  638.     -->
  639.     <!-- <buffer_profile>default</buffer_profile> -->
  640.  
  641.     <!-- Default database. -->
  642.     <default_database>default</default_database>
  643.  
  644.     <!-- Server time zone could be set here.
  646.          Time zone is used when converting between String and DateTime types,
  647.           when printing DateTime in text formats and parsing DateTime from text,
  648.           it is used in date and time related functions, if specific time zone was not passed as an argument.
  650.          Time zone is specified as identifier from IANA time zone database, like UTC or Africa/Abidjan.
  651.          If not specified, system time zone at server startup is used.
  653.          Please note, that server could display time zone alias instead of specified name.
  654.          Example: Zulu is an alias for UTC.
  655.     -->
  656.     <!-- <timezone>UTC</timezone> -->
  657.  
  658.     <!-- You can specify umask here (see "man umask"). Server will apply it on startup.
  659.          Number is always parsed as octal. Default umask is 027 (other users cannot read logs, data files, etc; group can only read).
  660.     -->
  661.     <!-- <umask>022</umask> -->
  662.  
  663.     <!-- Perform mlockall after startup to lower first queries latency
  664.           and to prevent clickhouse executable from being paged out under high IO load.
  665.          Enabling this option is recommended but will lead to increased startup time for up to a few seconds.
  666.     -->
  667.     <mlock_executable>true</mlock_executable>
  668.  
  669.     <!-- Reallocate memory for machine code ("text") using huge pages. Highly experimental. -->
  670.     <remap_executable>false</remap_executable>
  671.  
  672.     <![CDATA[
  673.          Uncomment below in order to use JDBC table engine and function.
  674.  
  675.          To install and run JDBC bridge in background:
  676.          * [Debian/Ubuntu]
  677.            export MVN_URL=https://repo1.maven.org/maven2/com/clickhouse/clickhouse-jdbc-bridge/
  678.            export PKG_VER=$(curl -sL $MVN_URL/maven-metadata.xml | grep '<release>' | sed -e 's|.*>\(.*\)<.*|\1|')
  679.            wget https://github.com/ClickHouse/clickhouse-jdbc-bridge/releases/download/v$PKG_VER/clickhouse-jdbc-bridge_$PKG_VER-1_all.deb
  680.            apt install --no-install-recommends -f ./clickhouse-jdbc-bridge_$PKG_VER-1_all.deb
  681.            clickhouse-jdbc-bridge &
  682.  
  683.          * [CentOS/RHEL]
  684.            export MVN_URL=https://repo1.maven.org/maven2/com/clickhouse/clickhouse-jdbc-bridge/
  685.            export PKG_VER=$(curl -sL $MVN_URL/maven-metadata.xml | grep '<release>' | sed -e 's|.*>\(.*\)<.*|\1|')
  686.            wget https://github.com/ClickHouse/clickhouse-jdbc-bridge/releases/download/v$PKG_VER/clickhouse-jdbc-bridge-$PKG_VER-1.noarch.rpm
  687.            yum localinstall -y clickhouse-jdbc-bridge-$PKG_VER-1.noarch.rpm
  688.            clickhouse-jdbc-bridge &
  689.  
  690.          Please refer to https://github.com/ClickHouse/clickhouse-jdbc-bridge#usage for more information.
  691.     ]]>
  692.     <!--
  693.     <jdbc_bridge>
  694.         <host>127.0.0.1</host>
  695.         <port>9019</port>
  696.     </jdbc_bridge>
  697.     -->
  698.  
  699.     <include_from>/etc/clickhouse-server/config.d/metrika.xml</include_from>
  700.  
  701.     <!-- Reloading interval for embedded dictionaries, in seconds. Default: 3600. -->
  702.     <builtin_dictionaries_reload_interval>3600</builtin_dictionaries_reload_interval>
  703.  
  704.  
  705.     <!-- Maximum session timeout, in seconds. Default: 3600. -->
  706.     <max_session_timeout>3600</max_session_timeout>
  707.  
  708.     <!-- Default session timeout, in seconds. Default: 60. -->
  709.     <default_session_timeout>60</default_session_timeout>
  710.  
  711.     <!-- Sending data to Graphite for monitoring. Several sections can be defined. -->
  712.     <!--
  713.         interval - send every X second
  714.         root_path - prefix for keys
  715.         hostname_in_path - append hostname to root_path (default = true)
  716.         metrics - send data from table system.metrics
  717.         events - send data from table system.events
  718.         asynchronous_metrics - send data from table system.asynchronous_metrics
  719.     -->
  720.     <!--
  721.     <graphite>
  722.         <host>localhost</host>
  723.         <port>42000</port>
  724.         <timeout>0.1</timeout>
  725.         <interval>60</interval>
  726.         <root_path>one_min</root_path>
  727.         <hostname_in_path>true</hostname_in_path>
  729.         <metrics>true</metrics>
  730.         <events>true</events>
  731.         <events_cumulative>false</events_cumulative>
  732.         <asynchronous_metrics>true</asynchronous_metrics>
  733.     </graphite>
  734.     <graphite>
  735.         <host>localhost</host>
  736.         <port>42000</port>
  737.         <timeout>0.1</timeout>
  738.         <interval>1</interval>
  739.         <root_path>one_sec</root_path>
  741.         <metrics>true</metrics>
  742.         <events>true</events>
  743.         <events_cumulative>false</events_cumulative>
  744.         <asynchronous_metrics>false</asynchronous_metrics>
  745.     </graphite>
  746.     -->
  747.  
  748.     <!-- Serve endpoint for Prometheus monitoring. -->
  749.     <!--
  750.         endpoint - mertics path (relative to root, statring with "/")
  751.         port - port to setup server. If not defined or 0 than http_port used
  752.         metrics - send data from table system.metrics
  753.         events - send data from table system.events
  754.         asynchronous_metrics - send data from table system.asynchronous_metrics
  755.         status_info - send data from different component from CH, ex: Dictionaries status
  756.     -->
  757.     <!--
  758.     <prometheus>
  759.         <endpoint>/metrics</endpoint>
  760.         <port>9363</port>
  762.         <metrics>true</metrics>
  763.         <events>true</events>
  764.         <asynchronous_metrics>true</asynchronous_metrics>
  765.         <status_info>true</status_info>
  766.     </prometheus>
  767.     -->
  768.  
  769.     <!-- Query log. Used only for queries with setting log_queries = 1. -->
  770.     <query_log>
  771.         <!-- What table to insert data. If table is not exist, it will be created.
  772.              When query log structure is changed after system update,
  773.               then old table will be renamed and new table will be created automatically.
  774.         -->
  775.         <database>system</database>
  776.         <table>query_log</table>
  777.         <!--
  778.             PARTITION BY expr: https://clickhouse.com/docs/en/table_engines/mergetree-family/custom_partitioning_key/
  779.             Example:
  780.                 event_date
  781.                 toMonday(event_date)
  782.                 toYYYYMM(event_date)
  783.                 toStartOfHour(event_time)
  784.         -->
  785.         <partition_by>toYYYYMM(event_date)</partition_by>
  786.         <!--
  787.             Table TTL specification: https://clickhouse.com/docs/en/engines/table-engines/mergetree-family/mergetree/#mergetree-table-ttl
  788.             Example:
  789.                 event_date + INTERVAL 1 WEEK
  790.                 event_date + INTERVAL 7 DAY DELETE
  791.                 event_date + INTERVAL 2 WEEK TO DISK 'bbb'
  793.         <ttl>event_date + INTERVAL 30 DAY DELETE</ttl>
  794.         -->
  795.  
  796.         <!-- Instead of partition_by, you can provide full engine expression (starting with ENGINE = ) with parameters,
  797.              Example: <engine>ENGINE = MergeTree PARTITION BY toYYYYMM(event_date) ORDER BY (event_date, event_time) SETTINGS index_granularity = 1024</engine>
  798.           -->
  799.  
  800.         <!-- Interval of flushing data. -->
  801.         <flush_interval_milliseconds>7500</flush_interval_milliseconds>
  802.     </query_log>
  803.  
  804.     <!-- Trace log. Stores stack traces collected by query profilers.
  805.          See query_profiler_real_time_period_ns and query_profiler_cpu_time_period_ns settings. -->
  806.     <trace_log>
  807.         <database>system</database>
  808.         <table>trace_log</table>
  809.  
  810.         <partition_by>toYYYYMM(event_date)</partition_by>
  811.         <flush_interval_milliseconds>7500</flush_interval_milliseconds>
  812.     </trace_log>
  813.  
  814.     <!-- Query thread log. Has information about all threads participated in query execution.
  815.          Used only for queries with setting log_query_threads = 1. -->
  816.     <query_thread_log>
  817.         <database>system</database>
  818.         <table>query_thread_log</table>
  819.         <partition_by>toYYYYMM(event_date)</partition_by>
  820.         <flush_interval_milliseconds>7500</flush_interval_milliseconds>
  821.     </query_thread_log>
  822.  
  823.     <!-- Query views log. Has information about all dependent views associated with a query.
  824.          Used only for queries with setting log_query_views = 1. -->
  825.     <query_views_log>
  826.         <database>system</database>
  827.         <table>query_views_log</table>
  828.         <partition_by>toYYYYMM(event_date)</partition_by>
  829.         <flush_interval_milliseconds>7500</flush_interval_milliseconds>
  830.     </query_views_log>
  831.  
  832.     <!-- Uncomment if use part log.
  833.          Part log contains information about all actions with parts in MergeTree tables (creation, deletion, merges, downloads).-->
  834.     <part_log>
  835.         <database>system</database>
  836.         <table>part_log</table>
  837.         <partition_by>toYYYYMM(event_date)</partition_by>
  838.         <flush_interval_milliseconds>7500</flush_interval_milliseconds>
  839.     </part_log>
  840.  
  841.     <!-- Uncomment to write text log into table.
  842.          Text log contains all information from usual server log but stores it in structured and efficient way.
  843.          The level of the messages that goes to the table can be limited (<level>), if not specified all messages will go to the table.
  844.     <text_log>
  845.         <database>system</database>
  846.         <table>text_log</table>
  847.         <flush_interval_milliseconds>7500</flush_interval_milliseconds>
  848.         <level></level>
  849.     </text_log>
  850.     -->
  851.  
  852.     <!-- Metric log contains rows with current values of ProfileEvents, CurrentMetrics collected with "collect_interval_milliseconds" interval. -->
  853.     <metric_log>
  854.         <database>system</database>
  855.         <table>metric_log</table>
  856.         <flush_interval_milliseconds>7500</flush_interval_milliseconds>
  857.         <collect_interval_milliseconds>1000</collect_interval_milliseconds>
  858.     </metric_log>
  859.  
  860.     <!--
  861.         Asynchronous metric log contains values of metrics from
  862.         system.asynchronous_metrics.
  863.     -->
  864.     <asynchronous_metric_log>
  865.         <database>system</database>
  866.         <table>asynchronous_metric_log</table>
  867.         <!--
  868.             Asynchronous metrics are updated once a minute, so there is
  869.             no need to flush more often.
  870.         -->
  871.         <flush_interval_milliseconds>7000</flush_interval_milliseconds>
  872.     </asynchronous_metric_log>
  873.  
  874.     <!--
  875.         OpenTelemetry log contains OpenTelemetry trace spans.
  876.     -->
  877.     <opentelemetry_span_log>
  878.         <!--
  879.             The default table creation code is insufficient, this <engine> spec
  880.             is a workaround. There is no 'event_time' for this log, but two times,
  881.             start and finish. It is sorted by finish time, to avoid inserting
  882.             data too far away in the past (probably we can sometimes insert a span
  883.             that is seconds earlier than the last span in the table, due to a race
  884.             between several spans inserted in parallel). This gives the spans a
  885.             global order that we can use to e.g. retry insertion into some external
  886.             system.
  887.         -->
  888.         <engine>
  889.             engine MergeTree
  890.             partition by toYYYYMM(finish_date)
  891.             order by (finish_date, finish_time_us, trace_id)
  892.         </engine>
  893.         <database>system</database>
  894.         <table>opentelemetry_span_log</table>
  895.         <flush_interval_milliseconds>7500</flush_interval_milliseconds>
  896.     </opentelemetry_span_log>
  897.  
  898.  
  899.     <!-- Crash log. Stores stack traces for fatal errors.
  900.          This table is normally empty. -->
  901.     <crash_log>
  902.         <database>system</database>
  903.         <table>crash_log</table>
  904.  
  905.         <partition_by />
  906.         <flush_interval_milliseconds>1000</flush_interval_milliseconds>
  907.     </crash_log>
  908.  
  909.     <!-- Session log. Stores user log in (successful or not) and log out events.
  911.         Note: session log has known security issues and should not be used in production.
  912.     -->
  913.     <!-- <session_log>
  914.         <database>system</database>
  915.         <table>session_log</table>
  917.         <partition_by>toYYYYMM(event_date)</partition_by>
  918.         <flush_interval_milliseconds>7500</flush_interval_milliseconds>
  919.     </session_log> -->
  920.  
  921.     <!-- Profiling on Processors level. -->
  922.     <processors_profile_log>
  923.         <database>system</database>
  924.         <table>processors_profile_log</table>
  925.  
  926.         <partition_by>toYYYYMM(event_date)</partition_by>
  927.         <flush_interval_milliseconds>7500</flush_interval_milliseconds>
  928.     </processors_profile_log>
  929.  
  930.     <!-- <top_level_domains_path>/var/lib/clickhouse/top_level_domains/</top_level_domains_path> -->
  931.     <!-- Custom TLD lists.
  932.          Format: <name>/path/to/file</name>
  934.          Changes will not be applied w/o server restart.
  935.          Path to the list is under top_level_domains_path (see above).
  936.     -->
  937.     <top_level_domains_lists>
  938.         <!--
  939.         <public_suffix_list>/path/to/public_suffix_list.dat</public_suffix_list>
  940.         -->
  941.     </top_level_domains_lists>
  942.  
  943.     <!-- Configuration of external dictionaries. See:
  944.          https://clickhouse.com/docs/en/sql-reference/dictionaries/external-dictionaries/external-dicts
  945.     -->
  946.     <dictionaries_config>*_dictionary.xml</dictionaries_config>
  947.  
  948.     <!-- Configuration of user defined executable functions -->
  949.     <user_defined_executable_functions_config>*_function.xml</user_defined_executable_functions_config>
  950.  
  951.     <!-- Uncomment if you want data to be compressed 30-100% better.
  952.          Don't do that if you just started using ClickHouse.
  953.       -->
  954.     <!--
  955.     <compression>
  956.         <!- - Set of variants. Checked in order. Last matching case wins. If nothing matches, lz4 will be used. - ->
  957.         <case>
  959.             <!- - Conditions. All must be satisfied. Some conditions may be omitted. - ->
  960.             <min_part_size>10000000000</min_part_size>        <!- - Min part size in bytes. - ->
  961.             <min_part_size_ratio>0.01</min_part_size_ratio>   <!- - Min size of part relative to whole table size. - ->
  963.             <!- - What compression method to use. - ->
  964.             <method>zstd</method>
  965.         </case>
  966.     </compression>
  967.     -->
  968.  
  969.     <!-- Configuration of encryption. The server executes a command to
  970.          obtain an encryption key at startup if such a command is
  971.          defined, or encryption codecs will be disabled otherwise. The
  972.          command is executed through /bin/sh and is expected to write
  973.          a Base64-encoded key to the stdout. -->
  974.     <encryption_codecs>
  975.         <!-- aes_128_gcm_siv -->
  976.             <!-- Example of getting hex key from env -->
  977.             <!-- the code should use this key and throw an exception if its length is not 16 bytes -->
  978.             <!--key_hex from_env="..."></key_hex -->
  979.  
  980.             <!-- Example of multiple hex keys. They can be imported from env or be written down in config-->
  981.             <!-- the code should use these keys and throw an exception if their length is not 16 bytes -->
  982.             <!-- key_hex id="0">...</key_hex -->
  983.             <!-- key_hex id="1" from_env=".."></key_hex -->
  984.             <!-- key_hex id="2">...</key_hex -->
  985.             <!-- current_key_id>2</current_key_id -->
  986.  
  987.             <!-- Example of getting hex key from config -->
  988.             <!-- the code should use this key and throw an exception if its length is not 16 bytes -->
  989.             <!-- key>...</key -->
  990.  
  991.             <!-- example of adding nonce -->
  992.             <!-- nonce>...</nonce -->
  993.  
  994.         <!-- /aes_128_gcm_siv -->
  995.     </encryption_codecs>
  996.  
  997.     <!-- Allow to execute distributed DDL queries (CREATE, DROP, ALTER, RENAME) on cluster.
  998.          Works only if ZooKeeper is enabled. Comment it if such functionality isn't required. -->
  999.     <distributed_ddl>
  1000.         <!-- Path in ZooKeeper to queue with DDL queries -->
  1001.         <path>/clickhouse/task_queue/ddl</path>
  1002.  
  1003.         <!-- Settings from this profile will be used to execute DDL queries -->
  1004.         <!-- <profile>default</profile> -->
  1005.  
  1006.         <!-- Controls how much ON CLUSTER queries can be run simultaneously. -->
  1007.         <!-- <pool_size>1</pool_size> -->
  1008.  
  1009.         <!--
  1010.              Cleanup settings (active tasks will not be removed)
  1011.         -->
  1012.  
  1013.         <!-- Controls task TTL (default 1 week) -->
  1014.         <!-- <task_max_lifetime>604800</task_max_lifetime> -->
  1015.  
  1016.         <!-- Controls how often cleanup should be performed (in seconds) -->
  1017.         <!-- <cleanup_delay_period>60</cleanup_delay_period> -->
  1018.  
  1019.         <!-- Controls how many tasks could be in the queue -->
  1020.         <!-- <max_tasks_in_queue>1000</max_tasks_in_queue> -->
  1021.     </distributed_ddl>
  1022.  
  1023.     <!-- Settings to fine tune MergeTree tables. See documentation in source code, in MergeTreeSettings.h -->
  1024.     <!--
  1025.     <merge_tree>
  1026.         <max_suspicious_broken_parts>5</max_suspicious_broken_parts>
  1027.     </merge_tree>
  1028.     -->
  1029.  
  1030.     <!-- Protection from accidental DROP.
  1031.          If size of a MergeTree table is greater than max_table_size_to_drop (in bytes) than table could not be dropped with any DROP query.
  1032.          If you want do delete one table and don't want to change clickhouse-server config, you could create special file <clickhouse-path>/flags/force_drop_table and make DROP once.
  1033.          By default max_table_size_to_drop is 50GB; max_table_size_to_drop=0 allows to DROP any tables.
  1034.          The same for max_partition_size_to_drop.
  1035.          Uncomment to disable protection.
  1036.     -->
  1037.     <!-- <max_table_size_to_drop>0</max_table_size_to_drop> -->
  1038.     <!-- <max_partition_size_to_drop>0</max_partition_size_to_drop> -->
  1039.  
  1040.     <!-- Example of parameters for GraphiteMergeTree table engine -->
  1041.     <graphite_rollup_example>
  1042.         <pattern>
  1043.             <regexp>click_cost</regexp>
  1044.             <function>any</function>
  1045.             <retention>
  1046.                 <age>0</age>
  1047.                 <precision>3600</precision>
  1048.             </retention>
  1049.             <retention>
  1050.                 <age>86400</age>
  1051.                 <precision>60</precision>
  1052.             </retention>
  1053.         </pattern>
  1054.         <default>
  1055.             <function>max</function>
  1056.             <retention>
  1057.                 <age>0</age>
  1058.                 <precision>60</precision>
  1059.             </retention>
  1060.             <retention>
  1061.                 <age>3600</age>
  1062.                 <precision>300</precision>
  1063.             </retention>
  1064.             <retention>
  1065.                 <age>86400</age>
  1066.                 <precision>3600</precision>
  1067.             </retention>
  1068.         </default>
  1069.     </graphite_rollup_example>
  1070.  
  1071.     <!-- Directory in <clickhouse-path> containing schema files for various input formats.
  1072.          The directory will be created if it doesn't exist.
  1073.       -->
  1074.     <format_schema_path>/var/lib/clickhouse/format_schemas/</format_schema_path>
  1075.  
  1076.     <!-- Default query masking rules, matching lines would be replaced with something else in the logs
  1077.         (both text logs and system.query_log).
  1078.         name - name for the rule (optional)
  1079.         regexp - RE2 compatible regular expression (mandatory)
  1080.         replace - substitution string for sensitive data (optional, by default - six asterisks)
  1081.     -->
  1082.     <query_masking_rules>
  1083.         <rule>
  1084.             <name>hide encrypt/decrypt arguments</name>
  1085.             <regexp>((?:aes_)?(?:encrypt|decrypt)(?:_mysql)?)\s*\(\s*(?:'(?:\\'|.)+'|.*?)\s*\)</regexp>
  1086.             <!-- or more secure, but also more invasive:
  1087.                 (aes_\w+)\s*\(.*\)
  1088.             -->
  1089.             <replace>\1(???)</replace>
  1090.         </rule>
  1091.     </query_masking_rules>
  1092.  
  1093.     <!-- Uncomment to use custom http handlers.
  1094.         rules are checked from top to bottom, first match runs the handler
  1095.             url - to match request URL, you can use 'regex:' prefix to use regex match(optional)
  1096.             methods - to match request method, you can use commas to separate multiple method matches(optional)
  1097.             headers - to match request headers, match each child element(child element name is header name), you can use 'regex:' prefix to use regex match(optional)
  1098.         handler is request handler
  1099.             type - supported types: static, dynamic_query_handler, predefined_query_handler
  1100.             query - use with predefined_query_handler type, executes query when the handler is called
  1101.             query_param_name - use with dynamic_query_handler type, extracts and executes the value corresponding to the <query_param_name> value in HTTP request params
  1102.             status - use with static type, response status code
  1103.             content_type - use with static type, response content-type
  1104.             response_content - use with static type, Response content sent to client, when using the prefix 'file://' or 'config://', find the content from the file or configuration send to client.
  1106.     <http_handlers>
  1107.         <rule>
  1108.             <url>/</url>
  1109.             <methods>POST,GET</methods>
  1110.             <headers><pragma>no-cache</pragma></headers>
  1111.             <handler>
  1112.                 <type>dynamic_query_handler</type>
  1113.                 <query_param_name>query</query_param_name>
  1114.             </handler>
  1115.         </rule>
  1117.         <rule>
  1118.             <url>/predefined_query</url>
  1119.             <methods>POST,GET</methods>
  1120.             <handler>
  1121.                 <type>predefined_query_handler</type>
  1122.                 <query>SELECT * FROM system.settings</query>
  1123.             </handler>
  1124.         </rule>
  1126.         <rule>
  1127.             <handler>
  1128.                 <type>static</type>
  1129.                 <status>200</status>
  1130.                 <content_type>text/plain; charset=UTF-8</content_type>
  1131.                 <response_content>config://http_server_default_response</response_content>
  1132.             </handler>
  1133.         </rule>
  1134.     </http_handlers>
  1135.     -->
  1136.  
  1137.     <send_crash_reports>
  1138.         <!-- Changing <enabled> to true allows sending crash reports to -->
  1139.         <!-- the ClickHouse core developers team via Sentry https://sentry.io -->
  1140.         <!-- Doing so at least in pre-production environments is highly appreciated -->
  1141.         <enabled>false</enabled>
  1142.         <!-- Change <anonymize> to true if you don't feel comfortable attaching the server hostname to the crash report -->
  1143.         <anonymize>false</anonymize>
  1144.         <!-- Default endpoint should be changed to different Sentry DSN only if you have -->
  1145.         <!-- some in-house engineers or hired consultants who're going to debug ClickHouse issues for you -->
  1146.         <endpoint>https://6f33034cfe684dd7a3ab9875e57b1c8d@o388870.ingest.sentry.io/5226277</endpoint>
  1147.     </send_crash_reports>
  1148.  
  1149.     <!-- Uncomment to disable ClickHouse internal DNS caching. -->
  1150.     <!-- <disable_internal_dns_cache>1</disable_internal_dns_cache> -->
  1151.  
  1152.     <!-- You can also configure rocksdb like this: -->
  1153.     <!--
  1154.     <rocksdb>
  1155.         <options>
  1156.             <max_background_jobs>8</max_background_jobs>
  1157.         </options>
  1158.         <column_family_options>
  1159.             <num_levels>2</num_levels>
  1160.         </column_family_options>
  1161.         <tables>
  1162.             <table>
  1163.                 <name>TABLE</name>
  1164.                 <options>
  1165.                     <max_background_jobs>8</max_background_jobs>
  1166.                 </options>
  1167.                 <column_family_options>
  1168.                     <num_levels>2</num_levels>
  1169.                 </column_family_options>
  1170.             </table>
  1171.         </tables>
  1172.     </rocksdb>
  1173.     -->
  1174.  
  1175.     <!-- Uncomment if enable merge tree metadata cache -->
  1176.     <!--merge_tree_metadata_cache>
  1177.         <lru_cache_size>268435456</lru_cache_size>
  1178.         <continue_if_corrupted>true</continue_if_corrupted>
  1179.     </merge_tree_metadata_cache-->
  1180. </clickhouse>

2.metrika.xml


在每个节点 /data/clickhouse/conf 目录下放入文件：metrika.xml，注意每个节点的副本名称都需要修改，不能冲突。本次我们搭建的是一个2节点，无副本的集群。

注意 所有节点/etc/hosts要把需要的zk和ck主机名配置进去。

  1. <?xml version="1.0"?>
  2. <yandex>
  3.     <remote_servers>
  4.         <!-- 单分片多副本集群 -->
  5.         <clickhouse_cluster> <!-- 集群名称 -->
  6.             <shard>
  7.                 <internal_replication>true</internal_replication>
  8.                 <replica>
  9.                     <host>bigdata1</host>
  10.                     <port>10000</port>  
  11.                     <user>clickhouse</user>
  12.                     <password>clickhouse</password>
  13.                 </replica>
  14.             </shard>
  15.             <shard>
  16.                 <internal_replication>true</internal_replication>
  17.                 <replica>
  18.                     <host>bigdata2</host>
  19.                     <port>10000</port>
  20.                     <user>clickhouse</user>
  21.                     <password>clickhouse</password>
  22.                 </replica>
  23.             </shard>
  24.         </clickhouse_cluster>
  25.     </remote_servers>
  26.  
  27.     <zookeeper>
  28.         <node index="1">
  29.             <host>bigdata1</host>
  30.             <port>2181</port>
  31.         </node>
  32.         <node index="2">
  33.             <host>bigdata2</host>
  34.             <port>2181</port>
  35.         </node>
  36.         <node index="3">
  37.             <host>bigdata3</host>
  38.             <port>2181</port>
  39.         </node>
  40.     </zookeeper>
  41.  
  42.     <!-- 宏变量 每个副本名称不能相同 shard理解违分片标志，replica所处的shard-->
  43.     <macros>
  44.         <shard>single</shard>
  45.         <replica>r1</replica> <!-- 每个节点的名称不同，依次：r1,r2,r3 -->
  46.     </macros>
  47. </yandex>

分片副本组合使用
在实际生产环境中，为了能够达到高可用，会对每个分片进行备份，即对每个节点的本地表进行备份，将分片和副本组合使用，组合的方式采用环形复制拓扑，充分利用两者的优势。如下图所示为一个 3 分片 + 1 副本的分布式表。

宏变量配置样例

  1. <!-- worker-01 配置 -->
  2. <macros>
  3.     <shard>01</shard>
  4.     <replica>03</replica>
  5.     <host>worker_01</host>
  6. </macros>
  7.  
  8. <!-- worker-02 配置 -->
  9. <macros>
  10.     <shard>02</shard>
  11.     <replica>01</replica>
  12.     <host>worker_02</host>
  13. </macros>
  14.  
  15. <!-- worker-03 配置 -->
  16. <macros>
  17.     <shard>03</shard>
  18.     <replica>02</replica>
  19.     <host>worker_03</host>
  20. </macros>

3.users.xml


在每个节点 /data/clickhouse/conf 目录下放入文件：users.xml，用于资源配置。

  1. <clickhouse>
  2.     <!-- See also the files in users.d directory where the settings can be overridden. -->
  3.  
  4.     <!-- Profiles of settings. -->
  5.     <profiles>
  6.         <!-- Default settings. -->
  7.         <default>
  8.             <max_memory_usage>10000000000</max_memory_usage>
  9.             <max_memory_usage_for_all_queries>10000000000</max_memory_usage_for_all_queries>
  10.             <max_execution_time>300</max_execution_time>
  11.             <max_bytes_before_external_group_by>5000000000</max_bytes_before_external_group_by>
  12.         </default>
  13.  
  14.         <!-- Profile that allows only read queries. -->
  15.         <readonly>
  16.             <readonly>1</readonly>
  17.         </readonly>
  18.     </profiles>
  19.  
  20.     <!-- Users and ACL. -->
  21.     <users>
  22.         <!-- If user name was not specified, 'default' user is used. -->
  23.         <default>
  24.             <!-- See also the files in users.d directory where the password can be overridden.
  26.                  Password could be specified in plaintext or in SHA256 (in hex format).
  28.                  If you want to specify password in plaintext (not recommended), place it in 'password' element.
  29.                  Example: <password>qwerty</password>.
  30.                  Password could be empty.
  32.                  If you want to specify SHA256, place it in 'password_sha256_hex' element.
  33.                  Example: <password_sha256_hex>65e84be33532fb784c48129675f9eff3a682b27168c0ea744b2cf58ee02337c5</password_sha256_hex>
  34.                  Restrictions of SHA256: impossibility to connect to ClickHouse using MySQL JS client (as of July 2019).
  36.                  If you want to specify double SHA1, place it in 'password_double_sha1_hex' element.
  37.                  Example: <password_double_sha1_hex>e395796d6546b1b65db9d665cd43f0e858dd4303</password_double_sha1_hex>
  39.                  If you want to specify a previously defined LDAP server (see 'ldap_servers' in the main config) for authentication,
  40.                   place its name in 'server' element inside 'ldap' element.
  41.                  Example: <ldap><server>my_ldap_server</server></ldap>
  43.                  If you want to authenticate the user via Kerberos (assuming Kerberos is enabled, see 'kerberos' in the main config),
  44.                   place 'kerberos' element instead of 'password' (and similar) elements.
  45.                  The name part of the canonical principal name of the initiator must match the user name for authentication to succeed.
  46.                  You can also place 'realm' element inside 'kerberos' element to further restrict authentication to only those requests
  47.                   whose initiator's realm matches it.
  48.                  Example: <kerberos />
  49.                  Example: <kerberos><realm>EXAMPLE.COM</realm></kerberos>
  51.                  How to generate decent password:
  52.                  Execute: PASSWORD=$(base64 < /dev/urandom | head -c8); echo "$PASSWORD"; echo -n "$PASSWORD" | sha256sum | tr -d '-'
  53.                  In first line will be password and in second - corresponding SHA256.
  55.                  How to generate double SHA1:
  56.                  Execute: PASSWORD=$(base64 < /dev/urandom | head -c8); echo "$PASSWORD"; echo -n "$PASSWORD" | sha1sum | tr -d '-' | xxd -r -p | sha1sum | tr -d '-'
  57.                  In first line will be password and in second - corresponding double SHA1.
  58.             -->
  59.             <password></password>
  60.  
  61.             <!-- List of networks with open access.
  63.                  To open access from everywhere, specify:
  64.                     <ip>::/0</ip>
  66.                  To open access only from localhost, specify:
  67.                     <ip>::1</ip>
  68.                     <ip>127.0.0.1</ip>
  70.                  Each element of list has one of the following forms:
  71.                  <ip> IP-address or network mask. Examples: 213.180.204.3 or 10.0.0.1/8 or 10.0.0.1/255.255.255.0
  72.                      2a02:6b8::3 or 2a02:6b8::3/64 or 2a02:6b8::3/ffff:ffff:ffff:ffff::.
  73.                  <host> Hostname. Example: server01.clickhouse.com.
  74.                      To check access, DNS query is performed, and all received addresses compared to peer address.
  75.                  <host_regexp> Regular expression for host names. Example, ^server\d\d-\d\d-\d\.clickhouse\.com$
  76.                      To check access, DNS PTR query is performed for peer address and then regexp is applied.
  77.                      Then, for result of PTR query, another DNS query is performed and all received addresses compared to peer address.
  78.                      Strongly recommended that regexp is ends with $
  79.                  All results of DNS requests are cached till server restart.
  80.             -->
  81.             <networks>
  82.                 <ip>::/0</ip>
  83.             </networks>
  84.  
  85.             <!-- Settings profile for user. -->
  86.             <profile>default</profile>
  87.  
  88.             <!-- Quota for user. -->
  89.             <quota>default</quota>
  90.  
  91.             <!-- User can create other users and grant rights to them. -->
  92.             <!-- <access_management>1</access_management> -->
  93.         </default>
  94.     </users>
  95.  
  96.     <!-- Quotas. -->
  97.     <quotas>
  98.         <!-- Name of quota. -->
  99.         <default>
  100.             <!-- Limits for time interval. You could specify many intervals with different limits. -->
  101.             <interval>
  102.                 <!-- Length of interval. -->
  103.                 <duration>3600</duration>
  104.  
  105.                 <!-- No limits. Just calculate resource usage for time interval. -->
  106.                 <queries>0</queries>
  107.                 <errors>0</errors>
  108.                 <result_rows>0</result_rows>
  109.                 <read_rows>0</read_rows>
  110.                 <execution_time>0</execution_time>
  111.             </interval>
  112.         </default>
  113.     </quotas>
  114. </clickhouse>

 也可以在命令行中创建用户：

create database if not exists tutorial;
CREATE ROLE dba;

GRANT all  ON *.* TO dba;
CREATE USER dba_u@'%' IDENTIFIED WITH sha256_password BY '密码';
GRANT dba TO dba_u; 
GRANT all  ON tutorial.* TO 'dba_u';

启动服务

docker-compose -f docker-compose.yml up -d clickhouse

  1. version: '2'
  2. services:
  3.   clickhouse:
  4.     container_name: clickhouse
  5.     image: clickhouse/clickhouse-server:22.9.7.34
  6.     restart: always
  7.     privileged: true
  8.     environment:
  9.       - TZ=Asia/Shanghai
  10.       - CLICKHOUSE_USER=clickhouse
  11.       - CLICKHOUSE_PASSWORD=clickhouse
  12.       - CLICKHOUSE_DEFAULT_ACCESS_MANAGEMENT=1
  13.     volumes:
  14.       - /data/clickhouse/data:/var/lib/clickhouse
  15.       - /data/clickhouse/logs:/var/log/clickhouse-server
  16.       - /data/clickhouse/conf/config.xml:/etc/clickhouse-server/config.xml
  17.       - /data/clickhouse/conf/users.xml:/etc/clickhouse-server/users.xml
  18.       - /data/clickhouse/conf/metrika.xml:/etc/clickhouse-server/config.d/metrika.xml
  19.       - /etc/hosts:/etc/hosts
  20.     hostname: bigdata1
  21.     ulimits:
  22.       nofile:
  23.         soft: 262144
  24.         hard: 262144
  25.     network_mode: 'host'

 来源：

https://www.cnblogs.com/chuijingjing/p/17051485.html

数据库 - ClickHouse安装及集群搭建 - 个人文章 - SegmentFault 思否

https://mp.weixin.qq.com/s/L0XIstgsrDiAGjhhhqoQrw

Clickhouse Docker集群部署

Docker快速搭建Clickhouse集群(3分片3副本) - 爱码网

验证：

创建本地表

MergeTree，这个引擎本身不具备同步副本的功能，如果指定的是ReplicaMergeTree，会同步到对应的replica上面去。一般在实际应用中，创建分布式表指定的都是Replica的表。

分布式表本身不存储数据，数据存储其实还是由本地表t_cluster完成的。这个dist_t_cluster仅仅做一个代理的作用。

如果在任意节点创建表以后，其他节点都能同步到表结构，说明集群生效。

CREATE TABLE default.test ON CLUSTER clickhouse_cluster
(
    name String DEFAULT 'lemonNan' COMMENT '姓名',
    age int DEFAULT 18 COMMENT '年龄',
    gongzhonghao String DEFAULT 'lemonCode' COMMENT '公众号',
    my_time DateTime64(3, 'UTC') COMMENT '时间'
) ENGINE = ReplacingMergeTree()
PARTITION BY toYYYYMM(my_time)
ORDER BY my_time

CREATE TABLE t_cluster ON CLUSTER clickhouse_cluster (
id Int16,
name String,
birth Date
)ENGINE = MergeTree()
PARTITION BY toYYYYMM(birth)

创建分布式表

CREATE TABLE default.dist_t_cluster ON CLUSTER clickhouse_cluster as t_cluster engine = Distributed(clickhouse_cluster, default, t_cluster, rand());

插入测试数据

多插入几条，在任意节点上查看分布式表，都能够看到数据。

insert into dist_t_cluster values(1, 'aaa', '2021-02-01'), (2, 'bbb', '2021-02-02');

客户端工具

大数据ClickHouse（二十）：ClickHouse 可视化工具操作 - 知乎

本文内容由网友自发贡献，转载请注明出处：【wpsshop博客】
推荐阅读
相关标签

Copyright © 2003-2013 www.wpsshop.cn 版权所有，并保留所有权利。

  

闽ICP备14008679号