Unable to Delete Unsynchronized Tables When Using dmctl binlog-schema delete

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: dmctl binlog-schema delete时无法删除取消同步的表

| username: AllinTiDB

【TiDB Usage Environment】Production\Test Environment\POC
【TiDB Version】v6.1.0
【Encountered Problem】
【Reproduction Path】What operations were performed to encounter the problem
【Problem Phenomenon and Impact】
【Attachments】

  • Relevant logs, configuration files, Grafana monitoring (https://metricstool.pingcap.com/)
  • TiUP Cluster Display information
  • TiUP Cluster Edit config information
  • TiDB-Overview monitoring
  • Corresponding module’s Grafana monitoring (if any, such as BR, TiDB-binlog, TiCDC, etc.)
  • Corresponding module logs (including logs one hour before and after the problem)

Starting component dmctl: /root/.tiup/components/dmctl/v6.1.0/dmctl/dmctl --master-addr 172.31.33.100:8261 binlog-schema delete -s mysql-data dmtask-data db_data db_table
{
“result”: true,
“msg”: “”,
“sources”: [
{
“result”: false,
“msg”: “[code=44009:class=schema-tracker:scope=internal:level=medium], Message: is not a valid CREATE TABLE statement, RawCause: [parser:1149]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use”,
“source”: “mysql-db_data”,
“worker”: “”
}
]
}


If the question is related to performance optimization or troubleshooting, please download the script and run it. Please select all and copy-paste the terminal output results and upload them.

| username: Meditator | Original post link

Syntax error提示

| username: AllinTiDB | Original post link

The problem I am encountering is that according to the official binlog-schema command, I use binlog-schema list to view a table synchronized by DM, and then use binlog-schema delete as specified (dmctl binlog-schema delete

[flags]), but it cannot be deleted. The first execution reports the following error:

Subsequent executions all report the following error:

Am I misunderstanding the binlog-schema command? How can I correctly delete a table that I do not want to synchronize in an ongoing DM task?

| username: yilong | Original post link

  1. Can the list of tables to be deleted be seen?
  2. Are the dmctl being used and the installed DM version consistent?
    The commands mainly refer to the documentation: 管理 TiDB Data Migration 迁移表的表结构 | PingCAP 文档中心
| username: wuxiangdong | Original post link

Is the source name incorrect? The error source is “source”: “mysql-db_data”, but it should be mysql-data.

| username: AllinTiDB | Original post link

  1. The list can be seen.
  2. The versions are all v6.1.0.
| username: AllinTiDB | Original post link

The source is correct, based on the information screenshot. This source has established multiple tasks, and other tasks did not use this table.

| username: Tank001 | Original post link

Has it been resolved now? What kind of problem is this?

| username: Hacker007 | Original post link

I also encountered these strange issues before. It was due to other tasks performing full synchronization. Once the synchronization is complete, it will automatically fix itself.

| username: AllinTiDB | Original post link

The issue is not resolved; it is still impossible to delete while synchronization is in progress.

| username: AllinTiDB | Original post link

In my scenario, DM synchronization is normal, but some tables need to be excluded from synchronization. Currently, it is not possible to exclude specific tables.

| username: okenJiang | Original post link

It looks like a bug. You can track the follow-up progress at binlog-schema delete is always failed · Issue #7373 · pingcap/tiflow · GitHub.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.