Keyspace Group TSO sync better consider all timestamp keys
Open
component/mcs
component/tso
type/enhancement
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 783
- Avg merge
- 5d 21h
- Merged PRs (30d)
- 36
Description
## Enhancement Task
Currently, only the PD leader TSO and the default keyspace group TSO service will read all timestamp keys with the prefix to get the greatest one as the latest. It would be better if we could treat the non-default keyspace group TSO start-up synchronization in the same way. By doing this, we could start and stop the TSO node more safely without considering the meta info cleanup.
Contributor guide
Assessment
This issue has not been assessed yet.