distributed/talent-plan-tinykv
1
0
Fork 0
mirror of https://github.com/talent-plan/tinykv.git synced 2024-12-26 12:50:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

Doc fix: fix dead links in project 2B and reading list (#436)

Browse Source 
* Fix dead link (#422)
This commit is contained in:
Yueyang Zhan 2023-01-06 09:22:50 +08:00 committed by GitHub
parent 584a2f5570
commit 2bcdc55c54
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/project2-RaftKV.md
View File

@ -93,7 +93,7 @@ First, the code that you should take a look at is `RaftStorage` located in `kv/
Then, here comes the core of TinyKV — raftstore. The structure is a little complicated, you can read the reference of TiKV to give you a better understanding of the design:
- <https://pingcap.com/blog-cn/the-design-and-implementation-of-multi-raft/#raftstore> (Chinese Version)
- <https://pingcap.com/blog/2017-08-15-multi-raft/#raftstore> (English Version)
- <https://pingcap.com/blog/design-and-implementation-of-multi-raft/#raftstore> (English Version)
The entrance of raftstore is `Raftstore`, see `kv/raftstore/raftstore.go`. It starts some workers to handle specific tasks asynchronously, and most of them aren’t used now so you can just ignore them. All you need to focus on is `raftWorker`.(kv/raftstore/raft_worker.go)

4
doc/reading_list.md
View File

@ -81,9 +81,9 @@
- Multi-Raft
- <https://tikv.org/deep-dive/scalability/multi-raft/>
- Split & Merge
- <https://pingcap.com/blog/2017-07-20-tidbinternal3/>
- <https://pingcap.com/blog/tidb-internal-scheduling/>
- Balance
- <https://pingcap.com/blog/2017-07-20-tidbinternal3/>
- <https://pingcap.com/blog/tidb-internal-scheduling/>
- Distributed Transactions
- Reading Materials
- Database Internals: 5. Transaction Processing and Recovery