This document introduces the configuration parameters for a TiDB Binlog drainer in Kubernetes.
The following table contains all configuration parameters available for the
tidb-drainer chart. Refer to Use Helm to learn how to configure these parameters.
|The name of |
|The name of the source TiDB cluster|
|The version of the source TiDB cluster|
|The base image of TiDB Binlog|
|The pulling policy of the image|
|The log level of the drainer process|
|The storage limit of the drainer Pod. Note that you should set a larger size if |
|Determines whether to disable casualty detection|
|Used to initialize a checkpoint if the drainer does not have one. The value is a string type, such as |
|Whether or not to enable TLS between clusters|
|The configuration file passed to the drainer. Detailed reference: drainer.toml||(see below)|
|The resource limits and requests of the drainer Pod|
|Ensures that the drainer Pod is only scheduled to the node with the specific key-value pair as the label. Detailed reference: nodeselector|
|Applies to drainer Pods, allowing the Pods to be scheduled to the nodes with specified taints. Detailed reference: taint-and-toleration|
|Defines scheduling policies and preferences of the drainer Pod. Detailed reference: affinity-and-anti-affinity|
The default value of
detect-interval = 10 compressor = "" [syncer] worker-count = 16 disable-dispatch = false ignore-schemas = "INFORMATION_SCHEMA,PERFORMANCE_SCHEMA,mysql" safe-mode = false txn-batch = 20 db-type = "file" [syncer.to] dir = "/data/pb"