Configuring Strong Data Consistency Between ClickHouse Replicas
This topic is available for MRS 3.3.0-LTS and later versions only.
Scenario
ClickHouse supports multiple replicas. When data is written to a local table, the data on the current node is updated immediately, but the data between other replicas is asynchronously updated.
Configure ClickHouse to ensure strong data consistency between replicas.
Parameters
The priority of configuring strong data consistency between ClickHouse replicas is as follows: single statements > sessions > global defaults.
Strong data consistency between replicas must be used together with atomicity. Otherwise, an exception occurs during data insertion and the rollback fails.
Log in to FusionInsight Manager and choose Cluster > Services > ClickHouse. Click Configurations then All Configurations, click Reliability, and search for and modify the following parameters.
Parameter |
Description |
---|---|
profiles.default.insert_quorum |
Whether to enable strong data consistency between ClickHouse replicas. The default value is 0, indicating that strong consistency between replicas is disabled. Value options are as follows: 0 to 9, auto, and all.
|
profiles.default.insert_quorum_timeout |
Timeout interval for writing strongly consistent data between replicas. The default value is 600000 ms. The value must be greater than 0. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot