Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

move some design docs to rfcs #5

Open
3 of 21 tasks
siddontang opened this issue Oct 22, 2018 · 2 comments
Open
3 of 21 tasks

move some design docs to rfcs #5

siddontang opened this issue Oct 22, 2018 · 2 comments

Comments

@siddontang
Copy link
Contributor

siddontang commented Oct 22, 2018 •
edited by huachaohuang

We have written many design docs internally, and we need to public them to let users know TiKV deeply.

  • Raft merge
  • Batch split Add batch split #6
  • ReadPool optimization
  • Remove region meta from etcd
  • Distributed GC
  • Batch message
  • Coprocessor chunk
  • Raft Local reader
  • Region heartbeat optimization
  • Follower/Leader read
  • Scheduling based on priority
  • API check for compatibility rolling update
  • Titan - a new engine for RocksDB
  • Titan GC
  • Joint consensus
  • lightning
  • PD simulator
  • PD schedule limit
  • Threaded Raftstore
  • Failpoint
  • Region Consistency check
@Hoverbear
Copy link
Contributor

Please label all PRs for this with the "Migrated RFC" tag so our team can know that it has already been accepted/implemented.

@tisonkun
Copy link
Contributor

cc @siddontang I'd like to see the design document of -

  • Joint consensus
  • Raft Local reader
  • Follower/Leader read

If any google docs or internal docs can be shared here, I'm glad to port them into English design document for archiving.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Hoverbear @siddontang @tisonkun