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 query of basic view cannot be completed on TiDB cluster V6.5.1 which is deployed on IPV6, due to compatibility issues #43286

Closed
adunhappy opened this issue Apr 21, 2023 · 2 comments · Fixed by #43815
Assignees
Labels

Comments

@adunhappy
Copy link

adunhappy commented Apr 21, 2023

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

image

mysql> select * from information_schema.cluster_processlist;
Empty set, 1 warning (40.62 sec)

mysql> show warnings;
+---------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Level | Code | Message |
+---------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Warning | 1105 | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: address 2409:8720:4a00:3:0:5:0:821:10080: too many colons in address" |
+---------+------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

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

IPV6 can be resolved normally and returne query results successfully.

3. What did you see instead (Required)

Unable to resolve IPV6, the following warning message is returned:rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: address 2409:8720:4a00:3:0:5:0:821:10080: too many colons in address"

4. What is your TiDB version? (Required)

mysql> select tidb_version();
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| tidb_version() |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Release Version: v6.5.1
Edition: Enterprise
Git Commit Hash: 4084b07
Git Branch: heads/refs/tags/v6.5.1
UTC Build Time: 2023-03-07 16:13:07
GoVersion: go1.19.5
Race Enabled: false
TiKV Min Version: 6.2.0-alpha
Check Table Before Drop: false
Store: tikv |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

@adunhappy adunhappy added the type/bug The issue is confirmed as a bug. label Apr 21, 2023
@adunhappy adunhappy changed the title 基于IPV6部署V6.5.1版本的TiDB集群,因兼容性问题无法完成基础视图的查询 The query of basic view cannot be completed on TiDB cluster V6.5.1 which is deployed on IPV6, due to compatibility issues Apr 22, 2023
@ti-chi-bot ti-chi-bot bot added may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 may-affects-7.1 labels Apr 23, 2023
@nexustar
Copy link
Contributor

It looks like a tikv bug

@Defined2014 Defined2014 added affects-6.5 affects-7.1 and removed may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 may-affects-7.1 labels May 15, 2023
@Defined2014 Defined2014 self-assigned this May 15, 2023
@Defined2014
Copy link
Contributor

This question is a bit interesting. I first tried it with Clash proxy on my computer, and no error was reported. It seems that Clash helped TiDB solve this problem. 😀

ti-chi-bot bot pushed a commit that referenced this issue May 15, 2023
ti-chi-bot bot pushed a commit that referenced this issue May 16, 2023
ti-chi-bot bot pushed a commit that referenced this issue May 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants