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

pagetable snapshotting #21

Closed
spacejam opened this issue Jul 16, 2017 · 1 comment
Closed

pagetable snapshotting #21

spacejam opened this issue Jul 16, 2017 · 1 comment
Assignees
Projects

Comments

@spacejam
Copy link
Owner

on recovery, we should be able to recover a snapshot of the pagetable, then read the log after the pagetable was created for full reconstruction. we only want to read and recover the structure of pages and the offsets of chunks of frags in the log for future retrieval, without pulling in any kv data.

initially this can be done by forking and snapshotting, similar to redis

@spacejam spacejam added this to the pagetable and LRU cache milestone Jul 16, 2017
@spacejam spacejam added this to thinking in v1 Jul 18, 2017
@spacejam spacejam moved this from thinking to back-burner in v1 Jul 19, 2017
@spacejam spacejam moved this from back-burner to doing in v1 Aug 11, 2017
@spacejam spacejam self-assigned this Aug 11, 2017
@spacejam
Copy link
Owner Author

ruling out the fork approach. with a large resident set size, forking could take a long time, and then we need to be really careful to avoid allocating memory (assume all mutexes are poisoned after forking). instead, re-use most of the code in PageCache::recover and have a thread write the snapshot without triggering a COW storm.

spacejam added a commit that referenced this issue Aug 14, 2017
@spacejam spacejam moved this from doing to done in v1 Aug 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
v1
  
done
Development

No branches or pull requests

1 participant