Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: 某个pd无法启动
|
username: Hacker_Sl3AGswc
[Test Environment for TiDB]
[TiDB Version] v6.5.4
[Encountered Issue: Problem Description and Impact]
A certain PD cannot start. In the error log, the following message is found: panic: tocommit(xxxx) is out of range [lastIndex(xxx)]. Was the raft log corrupted, truncated, or lost?
It looks a bit similar to this. You can try kicking this PD out first and then adding it back in.
This is generally caused by what reason? I solved it by scaling up and down.
Indeed, using the scale-out and scale-in method solves the problem faster.
Scale up or down, it seems like there is an issue with etcd.
If there are 3 PDs, definitely resolve it through scaling in and out.
The fastest way to solve it seems to be by scaling up and down.
It looks like the issue is caused by an interruption or loss of the etcd replication raft log at the PD layer, which could be due to hardware reasons or some incomplete bugs in PD. Could you please open an issue on GitHub?
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: