-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
The etcd client to the registry of Pump/Drainer info does not use auto-sync and fails when the PD cluster address changed #42643
Comments
In #9575 we added Lines 81 to 85 in 10f0093
(This might also manifest in the "MySQL-compatible AUTO_INCREMENT" feature #38809) Lines 588 to 591 in 00d48f9
While it is easy to just add back the option For now the lack of |
similar issue in other repos, |
Although the pump drainer has been maintained, it seems that other tool components (dm, cdc) may also have similar issues. Should we fix them all at once? @nongfushanquan @overvenus @lance6716 |
I think we can create a linter to found this problem. |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
SHOW PUMP STATUS;
2. What did you expect to see? (Required)
We see the status of the pump at step 6
3. What did you see instead (Required)
Context deadline exceeded in
etcd.(*Client).List
4. What is your TiDB version? (Required)
v4.0.14
The text was updated successfully, but these errors were encountered: