V0.12.1.x Fixes for sync: #573
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
- lower MASTERNODE_SYNC_THRESHOLD (4->2) - higher wait MASTERNODE_SYNC_TIMEOUT*2 and fail MASTERNODE_SYNC_TIMEOUT*5 timeouts for each step - ask at most MASTERNODE_SYNC_THRESHOLD*3 nodes for sync data - sync again 1 minute after last fail So we will ask at most 6 nodes and stop updating lastTime...s when we had data from at least 2 of them but will fail if we had nothing in 25 sec since current step start. In case of fail resync again faster.
eduffield222
pushed a commit
that referenced
this pull request
Sep 2, 2015
V0.12.1.x Fixes for sync:
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.
Fixes for sync:
MASTERNODE_SYNC_THRESHOLD(4->2)MASTERNODE_SYNC_TIMEOUT*2and failMASTERNODE_SYNC_TIMEOUT*5timeouts for each stepMASTERNODE_SYNC_THRESHOLD*3nodes for sync dataSo we will ask at most 6 nodes and stop updating lastTime...s when we had data from at least 2 of them but will fail if we had nothing in 25 sec since current step start.
In case of fail resync again faster.
EDIT: updated