TiKV max timestamp is not synchronized

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: TiKV max timestamp is not synced

| username: TiDBer_SIECnThv

[TiDB Usage Environment] Production Environment / Testing / Poc
[TiDB Version]
v1.11.0
[Reproduction Path] Operations performed that led to the issue
[Encountered Issue: Issue Phenomenon and Impact]
Prompt: TiKV max timestamp is not synced
[Resource Configuration]
16C24G
[Attachments: Screenshots/Logs/Monitoring]

Image
Image1164×530 9.13 KB

Image

2
| username: WalterWj | Original post link

Check the clocks on all servers.

3
| username: xfworld | Original post link

How is the cluster deployed? It looks like there is an issue with communication with PD.

What version is V1.11.0?

4
| username: Billmay表妹 | Original post link

Which version of TiDB is it?

5
| username: Billmay表妹 | Original post link

Is it possible that the nodes in the cluster have inconsistent times?
Check if all servers have clock update services to ensure accurate time.

6
| username: ShawnYan | Original post link

Similar:

7
| username: tidb菜鸟一只 | Original post link

I also think it might be that the clocks of the TiKV nodes are not synchronized. Did you synchronize the clocks of all the nodes?

8
| username: TiDBer_SIECnThv | Original post link

Deployed on a server with better performance.

9
| username: Billmay表妹 | Original post link

The answers above have covered it. First, check for any time inconsistency issues.

10
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.