Improve related documentation for stale/strong read and relative operation in cloud
Open
Nobody has claimed this yet.
area/scheduling
tracked
type/enhancement
type/refactor
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 1.2k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 31
Description
Change Request
This repository is ONLY used to solve problems related to DOCS-CN.
For other issues (TiDB, TiKV, etc), please move to other repositories.
Please answer the following questions before submitting your issue. Thanks!
- Describe what you find is inappropriate or missing in the existing docs.
Currently, the document about Stale Read and follower read is not friendly to users:
- Missing the docs about the session variables. such as
closest-replicas - Missing the docs on how to use it in the cluster deployed by
tidb-operator. - The feature
Stale ReadandFollower Readdo not describe at the same level. should beStalevsStrong,LeadervsFollower.
- Describe your suggestion or addition.
I will change relative documents.
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.
Assessment
This issue has not been assessed yet.