Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: pd server timeout
[TiDB Usage Environment] Production Environment
[TiDB Version] v5.3.3
[Reproduction Path] pd timeout
[Encountered Problem: Problem Phenomenon and Impact]
After rebuilding the pd cluster in the production environment, pd timeout frequently occurs.
The SQL has been printed out for you…
Did this SQL execute successfully in the end?
In the end, it still didn’t execute successfully.
Are all the PD nodes in a normal state? Check the logs of each PD node.
Oh, I suddenly found that there is a node that is
Is it possible that the clocks are not synchronized, and the difference is too large?
After adjusting the time, the problem still exists.
After making adjustments, you need to restart the node for them to take effect, right?
I’ve tried it. The strangest thing is that only some tables have this issue.
Hello,
Has the clock drift issue been fixed?
The tidb.log reports a tikv: PD timeout, please check the tikv logs for any clues.