Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: 日志分析
|
username: ffeenn
【TiDB Usage Environment】Production Environment
【TiDB Version】5.4.3
【Reproduction Path】What operations were performed when the issue occurred
【Encountered Issue: Problem Phenomenon and Impact】
Is this type of error log in tikv due to incorrect PD time?
【Resource Configuration】
Check the status and logs of PD. It seems that it is not communicating properly with PD.
Can you check if the store status is normal using pdctl? Alternatively, you can directly curl http://10.10.10.14:2379/pd/api/v1/stores (replace with your own PD node IP) to check the store status.
Prometheus also did not find any particular anomalies, but I did notice that one of the PD nodes has an issue with time zone queries. I’m not sure if this has any impact. Other than this error log, no other anomalies have been found in the cluster so far. Let’s study it further.
Different time zones will definitely cause issues with time synchronization. The time difference is too large, making it impossible to obtain the correct data.
If TiUP was used for installation, it would force a check on these configurations. The situation described is quite strange.
Hmm, I suspect that there was an error when Go was fetching the timezone, because this node couldn’t retrieve it. Go and timedatectl use the same method to get the timezone.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: 
|
username: 
|
username: