Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DM will report error when upstream MySQL has no data change #7037

Closed
lance6716 opened this issue Sep 9, 2022 · 2 comments · Fixed by #7542
Closed

DM will report error when upstream MySQL has no data change #7037

lance6716 opened this issue Sep 9, 2022 · 2 comments · Fixed by #7542
Labels
area/dm Issues or PRs related to DM. found/automation Bugs found by automation cases severity/moderate type/bug The issue is confirmed as a bug.

Comments

@lance6716
Copy link
Contributor

lance6716 commented Sep 9, 2022

What did you do?

When upstream has no data and enables GTID, its binlog position is at (mysql-bin.000001, 154) and has empty GTID set.

Then if user starts an all mode task...

[2022/09/09 06:17:52.285 +00:00] [INFO] [subtask.go:371] ["unit process returned"] [subtask=test-infra] [unit=Load] [stage=Finished] [status="{\"progress\":\"100.00 %\",\"metaBinlog\":\"(mysql-bin.000001, 154)\"}"]
[2022/09/09 06:17:52.285 +00:00] [INFO] [subtask.go:382] ["switching to next unit"] [subtask=test-infra] [unit=Load]
...
[2022/09/09 06:17:52.734 +00:00] [WARN] [syncer.go:3811] ["fail to get gtids for global location"] [task=test-infra] [unit="binlog replication"] [pos="position: (mysql-bin.000001, 154), gtid-set: "] [error="invalid position (mysql-bin.000001, 154) or GTID not enabled in upstream"] [errorVerbose="invalid position (mysql-bin.000001, 154) or GTID not enabled in upstream\ngithub.com/pingcap/tiflow/dm/pkg/binlog/reader.GetGTIDsForPosFromStreamer\n\tgithub.com/pingcap/tiflow/dm/pkg/binlog/reader/util.go:129\ngithub.com/pingcap/tiflow/dm/syncer.(*Syncer).adjustGlobalPointGTID\n\tgithub.com/pingcap/tiflow/dm/syncer/syncer.go:3809\ngithub.com/pingcap/tiflow/dm/syncer.(*Syncer).Run\n\tgithub.com/pingcap/tiflow/dm/syncer/syncer.go:1612\ngithub.com/pingcap/tiflow/dm/syncer.(*Syncer).Process\n\tgithub.com/pingcap/tiflow/dm/syncer/syncer.go:697\nruntime.goexit\n\truntime/asm_amd64.s:1571"]
[2022/09/09 06:17:52.736 +00:00] [INFO] [syncer.go:1501] ["received ungraceful exit ctx, exit now"] [task=test-infra] [unit="binlog replication"]
[2022/09/09 06:17:52.737 +00:00] [INFO] [subtask.go:371] ["unit process returned"] [subtask=test-infra] [unit=Sync] [stage=Paused] [status="{\"syncerBinlog\":\"(mysql-bin.000001, 154)\",\"binlogType\":\"remote\"}"]
[2022/09/09 06:17:52.737 +00:00] [ERROR] [subtask.go:392] ["unit process error"] [subtask=test-infra] [unit=Sync] ["error information"="ErrCode:50000 ErrClass:\"not-set\" ErrScope:\"not-set\" ErrLevel:\"high\" Message:\"invalid position (mysql-bin.000001, 154) or GTID not enabled in upstream\" "]

What did you expect to see?

No response

What did you see instead?

No response

Versions of the cluster

master

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

(paste current status of DM cluster here)
@lance6716 lance6716 added type/bug The issue is confirmed as a bug. area/dm Issues or PRs related to DM. labels Sep 9, 2022
@fubinzh
Copy link

fubinzh commented Sep 28, 2022

workaround: insert some data to upstream before starting dm task.

@fubinzh
Copy link

fubinzh commented Sep 30, 2022

/found automation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dm Issues or PRs related to DM. found/automation Bugs found by automation cases severity/moderate type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants