pingcap / pingcap/tidb-operator
Optimization for DNS queries
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
Is your feature request related to a problem? Please describe:
Currently, the addresses set for the components are like ns0-tikv-0.ns0-tikv-peer.ns0.svc, and the /etc/resolv.conf in the Pod is:
nameserver 10.233.0.10
search ns0.svc.cluster.local svc.cluster.local cluster.local
options ndots:5
so for each DNS query, it will go through the following queries:
ns0-tikv-0.ns0-tikv-peer.ns0.svc.ns0.svc.cluster.local
ns0-tikv-0.ns0-tikv-peer.ns0.svc.svc.cluster.local
ns0-tikv-0.ns0-tikv-peer.ns0.svc.cluster.local
This is unreasonable.
Describe the feature you'd like:
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides no source files, tests, or entry points to follow. Start by tracing how TiDB Operator constructs component addresses and Kubernetes service DNS names, then measure the current resolver queries shown in the issue. Done should mean the generated addresses avoid unnecessary search-domain queries without breaking cluster connectivity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100