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

Able to run TiDB components in host network #759

Closed
cofyc opened this issue Aug 12, 2019 · 2 comments · Fixed by #774
Closed

Able to run TiDB components in host network #759

cofyc opened this issue Aug 12, 2019 · 2 comments · Fixed by #774

Comments

@cofyc
Copy link
Contributor

cofyc commented Aug 12, 2019

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.

@tennix
Copy link
Member

tennix commented Aug 13, 2019

Currently, TiDB Operator uses domain names for each component. I think this should be still available when in host network mode.

@cofyc
Copy link
Contributor Author

cofyc commented Aug 13, 2019

yes, it resolves to node IP address.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants