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

replication lag not refreshed when last ddl is failed and skipped, and no futher ddl #9605

Closed
D3Hunter opened this issue Aug 18, 2023 · 1 comment · Fixed by #9607
Closed

Comments

@D3Hunter
Copy link
Contributor

What did you do?

  • start all mode task
  • in sync phase, run a ddl in upstream, and this ddl will fail on downstream
  • task will paused, skip the ddl, then start task

What did you expect to see?

lag will down to 0

What did you see instead?

lag keep increasing

Versions of the cluster

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

v5.4.1

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)
@D3Hunter
Copy link
Contributor Author

lag will down to 0 after execute another success ddl

ti-chi-bot pushed a commit to ti-chi-bot/tiflow that referenced this issue Aug 21, 2023
3AceShowHand pushed a commit to 3AceShowHand/tiflow that referenced this issue Aug 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants