-
Notifications
You must be signed in to change notification settings - Fork 283
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
gorouting & connection leak when relay meet error #6193
Labels
affects-2.0.5
affects-2.0.6
affects-2.0.7
affects-5.3
affects-5.4
affects-6.0
affects-6.1
area/dm
Issues or PRs related to DM.
severity/major
type/bug
The issue is confirmed as a bug.
Comments
GMHDBJD
added
type/bug
The issue is confirmed as a bug.
area/dm
Issues or PRs related to DM.
affects-5.3
affects-5.4
affects-6.0
affects-2.0.5
affects-2.0.6
affects-2.0.7
affects-6.1
labels
Jul 5, 2022
ti-chi-bot
pushed a commit
that referenced
this issue
Aug 19, 2022
This was referenced Aug 19, 2022
ti-chi-bot
added a commit
that referenced
this issue
Aug 19, 2022
ti-chi-bot
added a commit
that referenced
this issue
Aug 22, 2022
ti-chi-bot
added a commit
that referenced
this issue
Aug 23, 2022
This was referenced Aug 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-2.0.5
affects-2.0.6
affects-2.0.7
affects-5.3
affects-5.4
affects-6.0
affects-6.1
area/dm
Issues or PRs related to DM.
severity/major
type/bug
The issue is confirmed as a bug.
What did you do?
same relay config for different worker.
What did you expect to see?
no gorouting/connection leak
What did you see instead?
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: