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

[Lightning:DB:ErrInitErrManager]init error manager error: create conflict view failed: Error 1146 (42S02): table doesn't exist #11811

Open
GMHDBJD opened this issue Nov 27, 2024 · 1 comment · May be fixed by #11904
Labels
area/dm Issues or PRs related to DM. severity/moderate type/bug The issue is confirmed as a bug.

Comments

@GMHDBJD
Copy link
Contributor

GMHDBJD commented Nov 27, 2024

What did you do?

dm upstream switch job failed, see https://github.com/pingcap/tiflow/actions/runs/12035450530

What did you expect to see?

No response

What did you see instead?

No response

Versions of the cluster

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

master```
Upstream MySQL/MariaDB server version:
```console
(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)
@GMHDBJD GMHDBJD added area/dm Issues or PRs related to DM. severity/moderate type/bug The issue is confirmed as a bug. labels Nov 27, 2024
@lance6716
Copy link
Contributor

It's not caused by pingcap/tidb#57480 . Please attach TiDB log in GitHub actions artifacts to know what's happened

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. severity/moderate type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants