You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It starts as expected at 0-84533484-1054899238 and goes to next
(LogPos:0x20e899de)
decimal log pos 552114654 from bin-log
Data lengh 43940 characters data in that column json, data type BLOB
MariaDB SLAVE READ ONLY [database]> select sum(char_length(data)) from table where start_time = '2021-10-25 20:00:00' and title = 'TES TEST TEST' and game_id = 1303 and tstamp = '2021-10-25 20:03:36'\G
*************************** 1. row ***************************
sum(char_length(data)): 43940
What did you expect to see?
Smoth tidb dm repliction flow
What did you see instead?
Err: unsupport type 140 in binlog and don't know how to handle",
"RawCause": "",
"Workaround": "Please check if the binlog file could be parsed by mysqlbinlog."
Versions of the cluster
DM version (run dmctl -V or dm-worker -V or dm-master -V):
Thanks for reporting, currently we can't handle every type of MariaDB.
As you said "Data lengh 43940 characters data in that column json, data type BLOB", I don't understand what's the column type of that table (JSON or BLOB?). Can you post the table structure?
I found issue, it was compressed columns in the source DB. Issue not only with tables which used in dm replication, but with any compressed column in the source bin-log.
What did you do?
Tidb dm fails to read mariadb bin log
dmctl_task_status.txt
It starts as expected at 0-84533484-1054899238 and goes to next
(LogPos:0x20e899de)
decimal log pos 552114654 from bin-log
Data lengh 43940 characters data in that column json, data type BLOB
What did you expect to see?
Smoth tidb dm repliction flow
What did you see instead?
"Workaround": "Please check if the binlog file could be parsed by
mysqlbinlog
."Versions of the cluster
DM version (run
dmctl -V
ordm-worker -V
ordm-master -V
):Upstream MySQL/MariaDB server version:
MariaDB-server-10.3.31-1.el8.x86_64
How did you deploy DM: tiup or manually?
tiup
current status of DM cluster (execute
query-status
in dmctl)(paste current status of DM cluster here)
The text was updated successfully, but these errors were encountered: