From ce0753f9983915a5153173e51968937a11fb9c35 Mon Sep 17 00:00:00 2001 From: kennytm Date: Tue, 3 Sep 2024 14:12:48 +0800 Subject: [PATCH 1/2] dm: enable-relay is undeprecated since v5.4.0 --- dm/dm-source-configuration-file.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/dm/dm-source-configuration-file.md b/dm/dm-source-configuration-file.md index 103a509d15e7f..5de5ff77d3819 100644 --- a/dm/dm-source-configuration-file.md +++ b/dm/dm-source-configuration-file.md @@ -18,7 +18,7 @@ source-id: "mysql-replica-01" enable-gtid: false # Whether to enable relay log. -enable-relay: false # Since DM v2.0.2, this configuration item is deprecated. To enable the relay log feature, use the `start-relay` command instead. +enable-relay: false relay-binlog-name: "" # The file name from which DM-worker starts to pull the binlog. relay-binlog-gtid: "" # The GTID from which DM-worker starts to pull the binlog. # relay-dir: "relay-dir" # The directory used to store relay log. The default value is "relay-dir". This configuration item is marked as deprecated since v6.1 and replaced by a parameter of the same name in the dm-worker configuration. @@ -69,7 +69,7 @@ This section describes each configuration parameter in the configuration file. | :------------ | :--------------------------------------- | | `source-id` | Represents a MySQL instance ID. | | `enable-gtid` | Determines whether to pull binlog from the upstream using GTID. The default value is `false`. In general, you do not need to configure `enable-gtid` manually. However, if GTID is enabled in the upstream database, and the primary/secondary switch is required, you need to set `enable-gtid` to `true`. | -| `enable-relay` | Determines whether to enable the relay log feature. The default value is `false`. Since DM v2.0.2, this configuration item is deprecated. To [enable the relay log feature](/dm/relay-log.md#enable-and-disable-relay-log), use the `start-relay` command instead. | +| `enable-relay` | Determines whether to enable the relay log feature. The default value is `false`. Takes effect since DM v5.4. Additionally, you can [enable relay log dynamically](/dm/relay-log.md#enable-and-disable-relay-log) using the `start-relay` command. | | `relay-binlog-name` | Specifies the file name from which DM-worker starts to pull the binlog. For example, `"mysql-bin.000002"`. It only works when `enable_gtid` is `false`. If this parameter is not specified, DM-worker will start pulling from the earliest binlog file being replicated. Manual configuration is generally not required. | | `relay-binlog-gtid` | Specifies the GTID from which DM-worker starts to pull the binlog. For example, `"e9a1fc22-ec08-11e9-b2ac-0242ac110003:1-7849"`. It only works when `enable_gtid` is `true`. If this parameter is not specified, DM-worker will start pulling from the latest GTID being replicated. Manual configuration is generally not required. | | `relay-dir` | Specifies the relay log directory. | From 8b3e252f0f5431fa9cd748134db28e0b615a71ea Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Tue, 21 Jan 2025 20:11:10 +0800 Subject: [PATCH 2/2] Update dm/dm-source-configuration-file.md --- dm/dm-source-configuration-file.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dm/dm-source-configuration-file.md b/dm/dm-source-configuration-file.md index 5de5ff77d3819..a38bebfef82a2 100644 --- a/dm/dm-source-configuration-file.md +++ b/dm/dm-source-configuration-file.md @@ -69,7 +69,7 @@ This section describes each configuration parameter in the configuration file. | :------------ | :--------------------------------------- | | `source-id` | Represents a MySQL instance ID. | | `enable-gtid` | Determines whether to pull binlog from the upstream using GTID. The default value is `false`. In general, you do not need to configure `enable-gtid` manually. However, if GTID is enabled in the upstream database, and the primary/secondary switch is required, you need to set `enable-gtid` to `true`. | -| `enable-relay` | Determines whether to enable the relay log feature. The default value is `false`. Takes effect since DM v5.4. Additionally, you can [enable relay log dynamically](/dm/relay-log.md#enable-and-disable-relay-log) using the `start-relay` command. | +| `enable-relay` | Determines whether to enable the relay log feature. The default value is `false`. This parameter takes effect from v5.4. Additionally, you can [enable relay log dynamically](/dm/relay-log.md#enable-and-disable-relay-log) using the `start-relay` command. | | `relay-binlog-name` | Specifies the file name from which DM-worker starts to pull the binlog. For example, `"mysql-bin.000002"`. It only works when `enable_gtid` is `false`. If this parameter is not specified, DM-worker will start pulling from the earliest binlog file being replicated. Manual configuration is generally not required. | | `relay-binlog-gtid` | Specifies the GTID from which DM-worker starts to pull the binlog. For example, `"e9a1fc22-ec08-11e9-b2ac-0242ac110003:1-7849"`. It only works when `enable_gtid` is `true`. If this parameter is not specified, DM-worker will start pulling from the latest GTID being replicated. Manual configuration is generally not required. | | `relay-dir` | Specifies the relay log directory. |