[WIP] Use B+ tree for manifest structure. #113
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
part of #110
Now every read thread will acquire read lock for LevelControl for creating sst iterator. And if we update the files in one level, we need sort all files while holding a write lock and it will block all read thread. I hope I can propose a new structure so that we can update the sst file quickly so that it will not block other read thread too long.
Design
I use a four-level B+ Tree. If a compact job want to add or remove some files in one level (mostly the update files are continuously), it will copy every page it updates (for a four-level B+ Tree, it will copy and replace three pages). There are only tens record of every page, so that the update operation can be very fast.