Resync rewrite #18
Merged
Resync rewrite #18
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
I was connecting bestNode to the same bestNode.
Rewind ffldb best node if it is ahead of SQL db. Improve logging. Always scan to current best heigh, using rpc client call to getbestblock at the end of each iteration. This should now be good to plug into dcrdata daemon.
TODO: decide when to just nuke stake ffldb if it's far ahead of SQL db.
Closes 17.
|
Seems to work as intended. However, it's complicated and a big change. Now requires an on-disk ticket database (leveldb) to be able to get live tickets at the last recorded height before dcrdata exited. |
|
Also note that glide install is required before build as depends changed. |
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.
Addresses #17
This addresses the insane memory usage of rebuilddb. Maybe also resync from arbitrary height instead of 0.