From bfd844431dbbbcb6325073b6c5d8fa514442bd29 Mon Sep 17 00:00:00 2001 From: en-jin19 Date: Mon, 30 Aug 2021 12:29:44 +0200 Subject: [PATCH 1/2] TiDB Binlog config: update syncer.to.checkpoint info --- tidb-binlog/tidb-binlog-configuration-file.md | 25 ++++++++----------- 1 file changed, 10 insertions(+), 15 deletions(-) diff --git a/tidb-binlog/tidb-binlog-configuration-file.md b/tidb-binlog/tidb-binlog-configuration-file.md index dfd047f0efb60..102028f246176 100644 --- a/tidb-binlog/tidb-binlog-configuration-file.md +++ b/tidb-binlog/tidb-binlog-configuration-file.md @@ -335,22 +335,17 @@ When the downstream is Kafka, the valid configuration items are as follows: ### syncer.to.checkpoint -This section introduces a configuration item related to `syncer.to.checkpoint`. +* `type`: Specifies in what way the replication progress is saved. Currently, the available options are `mysql`, `tidb`, and `file`. -### type + This configuration item is the same as the downstream type by default. For example, when the downstream is `file`, the progress of the checkpoint is saved in the local file `/savepoint`; when the downstream is `mysql`, the progress is saved in the downstream database. If you need to explicitly specify using `mysql` or `tidb` to store the progress, make the following configuration: -* Specifies in what way the replication progress is saved. -* Available options: `mysql` and `tidb`. +* `schema`: `"tidb_binlog"` by default. -* Default value: The same as the downstream type. For example, when the downstream is `file`, the progress is saved in the local file system; when the downstream is `mysql`, the progress is saved in the downstream database. If you explicitly specify using `mysql` or `tidb` to store the progress, make the following configuration: + > **Note:** + > + > When deploying multiple Drainer nodes in the same TiDB cluster, you need to specify a different checkpoint schema for each node. Otherwise, the replication progress of two instances will overwrite each other. - * `schema`: `tidb_binlog` by default. - - > **Note:** - > - > When deploying multiple Drainer nodes in the same TiDB cluster, you need to specify a different checkpoint schema for each node. Otherwise, the replication progress of two instances will overwrite each other. - - * `host` - * `user` - * `password` - * `port` +* `host` +* `user` +* `password` +* `port` \ No newline at end of file From 2edc429bcd7954e17b5a9047c7ade0a39c426775 Mon Sep 17 00:00:00 2001 From: TomShawn <41534398+TomShawn@users.noreply.github.com> Date: Tue, 31 Aug 2021 15:11:43 +0800 Subject: [PATCH 2/2] Update tidb-binlog/tidb-binlog-configuration-file.md --- tidb-binlog/tidb-binlog-configuration-file.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-binlog/tidb-binlog-configuration-file.md b/tidb-binlog/tidb-binlog-configuration-file.md index 102028f246176..802ea1e85ece3 100644 --- a/tidb-binlog/tidb-binlog-configuration-file.md +++ b/tidb-binlog/tidb-binlog-configuration-file.md @@ -337,7 +337,7 @@ When the downstream is Kafka, the valid configuration items are as follows: * `type`: Specifies in what way the replication progress is saved. Currently, the available options are `mysql`, `tidb`, and `file`. - This configuration item is the same as the downstream type by default. For example, when the downstream is `file`, the progress of the checkpoint is saved in the local file `/savepoint`; when the downstream is `mysql`, the progress is saved in the downstream database. If you need to explicitly specify using `mysql` or `tidb` to store the progress, make the following configuration: + This configuration item is the same as the downstream type by default. For example, when the downstream is `file`, the checkpoint progress is saved in the local file `/savepoint`; when the downstream is `mysql`, the progress is saved in the downstream database. If you need to explicitly specify using `mysql` or `tidb` to store the progress, make the following configuration: * `schema`: `"tidb_binlog"` by default.