We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
pool-size = 0
Will check if task config file will also trigger this bug, at lease the job which is created by service has this problem
No response
DM version (run dmctl -V or dm-worker -V or dm-master -V):
dmctl -V
dm-worker -V
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):
SELECT tidb_version();
(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):
> >
query-status <task-name>
(paste current status of DM cluster here)
The text was updated successfully, but these errors were encountered:
/severity moderate
Sorry, something went wrong.
fixed by #7714
No branches or pull requests
What did you do?
Will check if task config file will also trigger this bug, at lease the job which is created by service has this problem
What did you expect to see?
No response
What did you see instead?
No response
Versions of the cluster
DM version (run
dmctl -V
ordm-worker -V
ordm-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)
The text was updated successfully, but these errors were encountered: