-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
select from information_schema returns "device or resource busy" for non-leader PD #37764
Comments
@kolbe where did you place the tidb-server that you run the SQL? Also in the us-east-1 region or other regions? The error message hint that this tidb-server cann't dial to "test-us-east-2-pd-0", this region probably has the new leader? |
The tidb-server where I run this SQL is in us-east-1.
PD leader is also in us-east-1:
|
According to https://github.com/pingcap/tidb/blob/master/store/helper/helper.go#L829 and from the error message, I think this tidb-server has contacted to all the pd in all regions, and just printed the last error it met. There maybe network isolation between this tidb server and all pd servers. |
I can confirm that the problem is not network isolation between this tidb-server instance and PD servers. I was able to contact the PD servers in us-east-1 and us-west-2 using curl logged into this tidb pod. |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
I altered the route tables in AWS so that my primary region (us-east-1, where the PD leader is located) has no route to a tertiary region.
2. What did you expect to see? (Required)
If a single PD member cannot be reached, but quorum remains and there is an active leader, queries to information_schema should still return results.
3. What did you see instead (Required)
tidb-server log:
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: