You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason is that we use a sync map to manage the connection between TiDB and PD. If TiDB has TLS config and PD uses HTTP schema, the pd client will trim the HTTP prefix when reading the key from the map. But when writing to the map, the key has a prefix. So it will read nothing about connection.
What version of PD are you using (pd-server -V)?
master
The text was updated successfully, but these errors were encountered:
Bug Report
What did you do?
Start a cse TiDB with TLS config.
What did you expect to see?
Everything is ok.
What did you see instead?
The reason is that we use a sync map to manage the connection between TiDB and PD. If TiDB has TLS config and PD uses HTTP schema, the pd client will trim the HTTP prefix when reading the key from the map. But when writing to the map, the key has a prefix. So it will read nothing about connection.
What version of PD are you using (
pd-server -V
)?master
The text was updated successfully, but these errors were encountered: