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

br restore doesn't tolerate error "[PD:client:ErrClientGetTSO]get TSO failed, tso client is nil" #58239

Closed
fubinzh opened this issue Dec 13, 2024 · 2 comments · Fixed by #58752
Labels
affects-7.5 This bug affects the 7.5.x(LTS) versions. affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-8.5 This bug affects the 8.5.x(LTS) versions. component/br This issue is related to BR of TiDB. severity/major type/bug The issue is confirmed as a bug.

Comments

@fubinzh
Copy link

fubinzh commented Dec 13, 2024

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. run br restore, there is a tmp error resulting in tso client not created successfully.

2. What did you expect to see? (Required)

br restore should be able to tolerate tmp error like this.

3. What did you see instead (Required)

br restore doesn't tolerate the tmp error
Image

4. What is your TiDB version? (Required)

v8.5.0

@fubinzh fubinzh added the type/bug The issue is confirmed as a bug. label Dec 13, 2024
@fubinzh
Copy link
Author

fubinzh commented Dec 13, 2024

/component br

@ti-chi-bot ti-chi-bot bot added the component/br This issue is related to BR of TiDB. label Dec 13, 2024
@lance6716
Copy link
Contributor

please help push PD side to fix this error completely

tikv/pd#8630

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-7.5 This bug affects the 7.5.x(LTS) versions. affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-8.5 This bug affects the 8.5.x(LTS) versions. component/br This issue is related to BR of TiDB. severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants