distributed/talent-plan-tinykv
1
0
Fork 0
mirror of https://github.com/talent-plan/tinykv.git synced 2025-03-24 16:50:37 +08:00
Code Issues Packages Projects Releases Wiki Activity

remove useless hints

Browse Source 
Signed-off-by: Connor1996 <zbk602423539@gmail.com>
This commit is contained in:
Connor1996 2020-04-28 16:38:10 +08:00 committed by Connor
parent d06e805544
commit 174028fc8a
1 changed files with 1 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
courses/project2-RaftKV.md
View File

@ -226,8 +226,3 @@ Then due to the log compaction, Raft module maybe needs to send a snapshot. `Pee
Then the snapshot will reflect in the next Raft ready, so the task you should do is to modify the raft ready process to handle the case of snapshot. When you are sure to apply the snapshot, you can update the peer storage’s memory state like `RaftLocalState`, `RaftApplyState` and `RegionLocalState`. Also don’t forget to persist these states to kvdb and raftdb and remove stale state from kvdb and raftdb. Besides, you also need to update
`PeerStorage.snapState` to `snap.SnapState_Applying` and send `runner.RegionTaskApply` task to region worker through `PeerStorage.regionSched` and wait until region worker finish.
> Hints:
>
> - If there are some committed entries to be executed in the apply worker, do not apply state, see `ReadyToHandlePendingSnap`.
> - Do not handle the next Raft ready before finishing applying snapshot.