系统变量 tidb_read_staleness 无效
Open
Nobody has claimed this yet.
area/scheduling
tracked
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 1.2k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 31
Description
File: /release-6.1/tidb-read-staleness.md
比如，如果该变量的值设置为 -5，TiDB 会在 5 秒时间范围内，保证 TiKV 拥有对应历史版本数据的情况下，选择尽可能新的一个时间戳。
5 秒时间范围内，也就是说：5秒前 到 现在，尽可能新的时间戳，那就是现在。
而预期的时间范围是：从开始 到 5秒前，尽可能新的时间戳。
AS OF TIMESTAMP正常，tidb_snapshot正常，tidb_read_staleness失败。
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 with release-6.1/tidb-read-staleness.md and read the documented semantics of tidb_read_staleness alongside the reported AS OF TIMESTAMP and tidb_snapshot behavior. Reproduce the -5-second case if a TiDB environment is available, then determine whether the documentation or variable behavior is inconsistent; done means the discrepancy is corrected or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases, documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100