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
One issue to run pods in host network is hostname is not pod name anymore. In Kubernetes, the hostname is set to the host hostname when the pod is running in host network (xref: kubernetes/kubernetes#12893). We need to update our start scripts to use pod name to construct the component address.
The text was updated successfully, but these errors were encountered:
Feature Request
Is your feature request related to a problem? Please describe:
In GKE TiDB sysbench benchmark, performance in the host network is slightly better (10%) than the pod network (GKE cluster network is VPC-native).
Describe the feature you'd like:
Able to run TiDB components (pd/tidb/tikv) in host network.
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
One issue to run pods in host network is hostname is not pod name anymore. In Kubernetes, the hostname is set to the host hostname when the pod is running in host network (xref: kubernetes/kubernetes#12893). We need to update our start scripts to use pod name to construct the component address.
The text was updated successfully, but these errors were encountered: