Greenplum Except for the initial 3 nodes, the Greenplum cluster is deployed using an additional master node. Each segment server contains 8 segments, which means 4 segments per NVMe SSD. So there are S3 1. In Aurora, query the current binlog position by running the following command: mysql> SHOW MASTER STATUS; 195 The output is similar to the following. Record the binlog name and position for later upstream MySQL �→ must also enable GTID. If the upstream MySQL service is �→ configured to switch master between different nodes automatically �→ , GTID mode is required. enable-gtid: false from: host:

when GTID is empty in the upstream #3731 • Fix the issue that empty configurations may cause dm-master to panic #3732 • TiDB Lightning • Fix the issue that the precheck does not check local disk resources S3 1. In Aurora, query the current binlog position by running the following command: mysql> SHOW MASTER STATUS; The output is similar to the following. Record the binlog name and position for later use upstream MySQL �→ must also enable GTID. If the upstream MySQL service is �→ configured to switch master between different nodes automatically �→ , GTID mode is required. enable-gtid: false from: host:

set @@tidb_allow_mpp=1; set @@tidb_mem_quota_query = 10 << 30; Greenplum 配置 Greenplum 集群使用额外的一台 Master 节点部署（共四台），每台 Segment Server 部署 8 Segments（每个 NVMe SSD 各 4 个），总共 24 Segments。存储格式为 append-only / 列式存储，分区键为主键。 5.3.1.2.1 第 1 步：导出 Aurora 快照文件到 Amazon S3 1. 在 Aurora 上，执行以下命令，查询并记录当前 binlog 位置： mysql> SHOW MASTER STATUS; 你将得到类似以下的输出，请记录 binlog 名称和位置，供后续步骤使用： +------------------+----------+--------------+-- dmctl 将数据源配置加载到 DM 集群中: tiup dmctl --master-addr ${advertise-addr} operate-source create source1.yaml 该命令中的参数描述如下： 参数 描述 --master-addr dmctl 要连接的集群的任意 DM-master 节点的 {advertise-addr}，例如：172.16.10.71:8261

S3 1. In Aurora, query the current binlog position by running the following command: mysql> SHOW MASTER STATUS; The output is similar to the following. Record the binlog name and position for later use upstream MySQL �→ must also enable GTID. If the upstream MySQL service is �→ configured to switch master between different nodes automatically �→ , GTID mode is required. enable-gtid: false from: host: tiup dmctl --master-addr ${advertise-addr} operate-source create �→ source1.yaml The parameters used in the command above are described as follows: 710 Parameter Description -- �→ master �→ - �→ addr

following methods: • Encrypt using a custom fixed key • Encrypt using a master key stored on a local disk • Encrypt using a master key managed by a Key Management Service (KMS) For more information, see Change type Description BR -- �→ master �→ -key Newly added Specifies the master key for log backup data. It can be a master key stored on a local disk or a master key managed by a cloud Key Manage- parame- ter Change type Description BR -- �→ master �→ -key �→ - �→ crypter �→ - �→ method �→ Newly added Specifies the en- cryption algo- rithm based on the master key for log backup data, which can be aes128-

subsequent incremental migration. In Amazon Aurora, run the SHOW MASTER STATUS command and record the current binlog position: SHOW MASTER STATUS; The output is similar to the following. Record the binlog upstream MySQL �→ must also enable GTID. If the upstream MySQL service is �→ configured to switch master between different nodes automatically �→ , GTID mode is required. enable-gtid: false from: host: tiup dmctl --master-addr ${advertise-addr} operate-source create �→ source1.yaml The parameters used in the command above are described as follows: Parameter Description -- �→ master �→ - �→ addr �→

following methods: • Encrypt using a custom fixed key • Encrypt using a master key stored on a local disk • Encrypt using a master key managed by a Key Management Service (KMS) For more information, see Change type Description BR -- �→ master �→ -key Newly added Specifies the master key for log backup data. It can be a master key stored on a local disk or a master key managed by a cloud Key Manage- parame- ter Change type Description BR -- �→ master �→ -key �→ - �→ crypter �→ - �→ method �→ Newly added Specifies the en- cryption algo- rithm based on the master key for log backup data, which can be aes128-

subsequent incremental migration. In Amazon Aurora, run the SHOW MASTER STATUS command and record the current binlog position: SHOW MASTER STATUS; The output is similar to the following. Record the binlog upstream MySQL �→ must also enable GTID. If the upstream MySQL service is �→ configured to switch master between different nodes automatically �→ , GTID mode is required. enable-gtid: false from: host: tiup dmctl --master-addr ${advertise-addr} operate-source create �→ source1.yaml The parameters used in the command above are described as follows: Parameter Description -- �→ master �→ - �→ addr �→

subsequent incremental migration. In Amazon Aurora, run the SHOW MASTER STATUS command and record the current binlog position: SHOW MASTER STATUS; The output is similar to the following. Record the binlog upstream MySQL �→ must also enable GTID. If the upstream MySQL service is �→ configured to switch master between different nodes automatically �→ , GTID mode is required. enable-gtid: false from: host: tiup dmctl --master-addr ${advertise-addr} operate-source create �→ source1.yaml The parameters used in the command above are described as follows: Parameter Description -- �→ master �→ - �→ addr �→

#5063 * 修复 DM Web UI offline 选项及其他使用问题 #4993 * 修复上游 GTID 配置为空时，增量任务启动失败的问题 #3731 * 修复空配置可能导致 dm-master panic 的问题 #3732 – TiDB Lightning * 修复前置检查中没有检查本地磁盘空间以及集群是否可用的问题 #34213 * 修复 schema 路由错误的问题 #33381 6.3.1.2.1 第 1 步：导出 Aurora 快照文件到 Amazon S3 1. 在 Aurora 上，执行以下命令，查询并记录当前 binlog 位置： mysql> SHOW MASTER STATUS; 你将得到类似以下的输出，请记录 binlog 名称和位置，供后续步骤使用： +------------------+----------+--------------+-- dmctl 将数据源配置加载到 DM 集群中: tiup dmctl --master-addr ${advertise-addr} operate-source create source1.yaml 该命令中的参数描述如下： 参数 描述 --master-addr dmctl 要连接的集群的任意 DM-master 节点的 {advertise-addr}，例如：172.16.10.71:8261