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

The etcd client to the registry of Pump/Drainer info does not use auto-sync and fails when the PD cluster address changed #1236

Closed
lance6716 opened this issue May 31, 2023 · 0 comments · Fixed by #1240

Comments

@lance6716
Copy link
Contributor

copied from pingcap/tidb#42643


Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. Start a TiDB cluster with 3 PDs ① ② ③ and a Pump connected
  2. Scale-out 3 more PDs ④ ⑤ ⑥
  3. Wait 31 seconds
  4. Scale-in the original PDs ① ② ③
  5. Wait 31 seconds
  6. Run 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

@ti-chi-bot ti-chi-bot bot closed this as completed in #1240 Jun 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment