resolved TS may go backwards
Open
type/bug
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 783
- Avg merge
- 5d 21h
- Merged PRs (30d)
- 36
Description
## Bug Report
### What did you do?
just check the code. in `CheckAndUpdateMinResolvedTS`, after the atomic variable is updated the new value is visible.
https://github.com/tikv/pd/blob/4a11b99ee113c3f18dcd93623bb591a458d078c1/server/cluster/cluster.go#L2301-L2302
but at that point it's not persisited. So after reboot the old value will be exposed
https://github.com/tikv/pd/blob/4a11b99ee113c3f18dcd93623bb591a458d078c1/server/cluster/cluster.go#L2324-L2325
### What did you expect to see?
### What did you see instead?
### What version of PD are you using (`pd-server -V`)?
Contributor guide
Assessment
This issue has not been assessed yet.