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

warn/error count limit for check-task/start-task has wrong granularity #11587

Open
lance6716 opened this issue Sep 10, 2024 · 1 comment
Open

Comments

@lance6716
Copy link
Contributor

What did you do?

Sometime a checking item level is "warn", but internal errors list level is "fail"
image
image

in below case, when we only limit to output 1 error (foe example, by check-task ... --error 1), DM will only output suberror a. But it's better to output check item B

- check item A, warn
   - suberror a, fail
   - suberror b, fail
- check item B, fail 

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):

(paste DM version here, and you must ensure versions of dmctl, DM-worker and DM-master are same)

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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant