Major Description
Hi, We have discovered that the problem we reported earlier is still recurring. The problem is that a multi-replica cluster may fail to restart after transfering a outdated snapshot
Upon further investigation, we found that the issue originates from the resetClient function. Specifically, there is a flaw in its logic that causes it to incorrectly set the nextIndex of followers to 0, which leads to the error message shown in the attached screenshot.
Upon reviewing the code, we determined that the issue arose only after merging the PR. Surprisingly, the code was correct prior to merging.
After investigating further, we determined that the solution was to remove the index judgment, as the conditions onError and request == null were sufficient to encompass the required test conditions.
PTAL~szetszwo
