DM: failed to mock downstream table by create table statement in schema tracker

[GMHDBJD]

What did you do?

create table with shard_row_id_bits and primary int key(tidb_enable_clusterd_index: INT_ONLY) in downstream

What did you expect to see?

dm runs well

What did you see instead?

[2023/12/14 10:49:47.826 +08:00] [ERROR] [tracker.go:413] ["Init dowstream schema info error. "] [task=dglp_g1] [unit="binlog replication"] [tableID=ti_dglpdb.TM_GL_TXN_ITEM] [error="[code=44018:class=schema-tracker:scope=internal:level=high], Message: failed to mock downstream table by create table statement in schema tracker, RawCause: [ddl:8200]Unsupported shard_row_id_bits for table with primary key as row id\ngithub.com/pingcap/tiflow/dm/pkg/terror.(*Error).Delegate\n\tgithub.com/pingcap/tiflow/dm/pkg/terror/terror.go:324\ngithub.com/pingcap/tiflow/dm/pkg/schema.(*downstreamTracker).getTableInfoByCreateStmt\n\tgithub.com/pingcap/tiflow/dm/pkg/schema/tracker.go:469\ngithub.com/pingcap/tiflow/dm/pkg/schema.(*downstreamTracker).getOrInit\n\tgithub.com/pingcap/tiflow/dm/pkg/schema/tracker.go:411\ngithub.com/pingcap/tiflow/dm/pkg/schema.(*Tracker).GetDownStreamTableInfo\n\tgithub.com/pingcap/tiflow/dm/pkg/schema/tracker.go:383\ngithub.com/pingcap/tiflow/dm/syncer.(*Syncer).genAndFilterInsertDMLs\n\tgithub.com/pingcap/tiflow/dm/syncer/dml.go:113\ngithub.com/pingcap/tiflow/dm/syncer.(*Syncer).handleRowsEvent\n\tgithub.com/pingcap/tiflow/dm/syncer/syncer.go:2554\ngithub.com/pingcap/tiflow/dm/syncer.(*Syncer).Run\n\tgithub.com/pingcap/tiflow/dm/syncer/syncer.go:2307\ngithub.com/pingcap/tiflow/dm/syncer.(*Syncer).Process\n\tgithub.com/pingcap/tiflow/dm/syncer/syncer.go:734\ngithub.com/pingcap/tiflow/dm/syncer.(*Syncer).Resume\n\tgithub.com/pingcap/tiflow/dm/syncer/syncer.go:3197\nruntime.goexit\n\truntime/asm_amd64.s:1594"]

Versions of the cluster

DM version (run dmctl -V or dm-worker -V or dm-master -V):

v6.5.3

Upstream MySQL/MariaDB server version:

(paste upstream MySQL/MariaDB server version here)

Downstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):

(paste TiDB cluster version here)

How did you deploy DM: tiup or manually?

(leave TiUP or manually here)

Other interesting information (system version, hardware config, etc):

>
>

current status of DM cluster (execute query-status <task-name> in dmctl)

(paste current status of DM cluster here)

[seiya-annie]

/found customer