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.

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

Phase2: use WAL for log to boost log performance #14

Open
liuluheng opened this issue Jun 25, 2017 · 0 comments
Open

Phase2: use WAL for log to boost log performance #14

liuluheng opened this issue Jun 25, 2017 · 0 comments
Assignees
Milestone

Comments

@liuluheng
Copy link
Collaborator

liuluheng commented Jun 25, 2017

Plan/Roadmap

3 stages

  1. hack sqlite (wal/parser) and NPLRuntime to get the wal data(may be frame) as the raft log.(35 days)

    • wal_page_hook. actordb uses tcp socket to get the wal data, we can try to use stack in NPL to get the data.
    • checkponit hook.
    • options that enable these hooks to make sqlite independent. This is at database level, may use PRAGMA or modify NPLRuntime.
    • this stage may works in NPLRuntime repo.
  2. reorganize the Raft implementation to adapt to the wal, include deal with the sqlite checkpoint.(40 days)

    • replicate the wal data, may reconsider RPC.
    • deal with term and logIndex
    • deal with checkpoint. like packLog in the current implementation.
    • much work in this stage
  3. test the throuput and fix.(15 days)

@liuluheng liuluheng self-assigned this Jun 25, 2017
@LiXizhi LiXizhi added this to the Alpha2 milestone Jul 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants