mv-iterator-refresh (part 2) #114
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
matthewvon
pushed a commit
that referenced
this pull request
Dec 20, 2013
mv-iterator-refresh (part 2)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add option for iterator_refresh, which is currently implemented in eleveldb.
Eleveldb does the following: when an iterator is held for a long, long time AND its database (vnode) is under heavy write load, the snapshot held by the iterator can cause that database thrash. If this iterator is ONLY processing NEXT operations, this branch will close and reopen the iterator every 5 minutes. Intended primarily for internal Riak operations such as AAE.
Notes here: https://github.com/basho/leveldb/wiki/mv-iterator-refresh