-
Notifications
You must be signed in to change notification settings - Fork 498
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 backup could raise error when PD leader changed during BR initialization #5630
Comments
it should resolve to other PD members in different DNS lookup calls. |
@csuzhangxc what is actually seen from the log is that we received a DNS lookup error from CDC:
is there any chance that switching PD leader will cause the DNS to report NXDOMAIN or return with zero A/AAAA records in the ANSWER section? |
NO, can not resolve DNS should often be caused by the PD pod being down (or KubeDNS having problems) |
Bug Report
What version of Kubernetes are you using?
What version of TiDB Operator are you using?
What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?
What's the status of the TiDB cluster pods?
What did you do?
error=\"pd address not available, ..., dial tcp: lookup <pd addr>: no such host, please check network
What did you expect to see?
BR is able to run when PD leader is offline during discovery
What did you see instead?
BR failed and raised an error
The text was updated successfully, but these errors were encountered: