optimize: raft mode maintains the reload logic consistent with the file #7027
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?
存在于file一样的缺点,reload后会删除failed状态的事务及涉及的分支事务和锁
以及reload时机于file有区别,file是在重启时,而raft是在leader选举后进行reload(一般leader重选举就是leader挂了)
It has the same drawbacks as in the file: after reload, failed transactions, associated branch transactions, and locks will be deleted. Additionally, the timing of the reload differs from that of the file; the file reload occurs during a restart, while the RAFT reload happens after a leader election (usually, the leader re-election occurs when the leader has failed).
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews