The query of basic view cannot be completed on TiDB cluster V6.5.1 which is deployed on IPV6, due to compatibility issues

[adunhappy]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

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)

[nexustar]

It looks like a tikv bug

[Defined2014]

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. 😀