pingcap / pingcap/tidb-operator
Optimize tidb availability test
Open
Nobody has claimed this yet.
v2
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Only test whether connections are unexpectedly closed. No need to test the SQL latency
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
Start by locating the TiDB availability test in the repository and read its current checks. Remove the SQL latency check while retaining coverage for connections that are unexpectedly closed, then run the relevant availability test to confirm it still passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100