-
Notifications
You must be signed in to change notification settings - Fork 795
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
Lazy bootstrap retry limit #2362
Merged
SergiySW
merged 37 commits into
nanocurrency:master
from
SergiySW:bootstrap/lazy_retry_limit
Oct 31, 2019
Merged
Lazy bootstrap retry limit #2362
SergiySW
merged 37 commits into
nanocurrency:master
from
SergiySW:bootstrap/lazy_retry_limit
Oct 31, 2019
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
Also process all lazy destinations instead of only top destinations
- stop lazy bootstrap with stopped node - use bootstrap network params - improve lock in process_block_lazy () - increase max lazy bootstrap duration
cryptocode
approved these changes
Oct 24, 2019
wezrule
approved these changes
Oct 24, 2019
guilhermelawless
approved these changes
Oct 24, 2019
argakiig
approved these changes
Oct 30, 2019
argakiig
pushed a commit
that referenced
this pull request
Oct 31, 2019
- different retry limit for lazy destinations and possible links from state blocks (add retry limit to nano::bulk_pull) - start lazy pulls for all known destinations in lazy bootstrap attempt - dynamic bulk pull blocks limit for lazy bootstrap based on lazy blocks ratio (total processed blocks / lazy blocks) - don't clean unchecked for longest bootstrap attempts - use bootstrap network params - improve lock in process_block_lazy () - increase max lazy bootstrap duration - change max lazy keys limit - increase bootstrap_max_new_connections - fix: stop lazy bootstrap with stopped node - fix: proper reuse of of connections after lazy pull stop
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
quality improvements
This item indicates the need for or supplies changes that improve maintainability
rpc
Changes related to Remote Procedure Calls
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.
-RPC change in v20: more data in bootstrap_status