Skip to content
This repository has been archived by the owner on Aug 16, 2021. It is now read-only.

[BlockStore] ProcessPendingStorage should download and persist new blocks immediately #392

Closed
fassadlr opened this issue Aug 31, 2017 · 1 comment

Comments

@fassadlr
Copy link
Collaborator

fassadlr commented Aug 31, 2017

When a new block arrives from consensus, it needs to be downloaded and pushed to the repository immediately so that other peers can have access to it.

Currently, we will wait for a 100 blocks to download OR 200secs before we push to the repository.

@dangershony
Copy link
Contributor

Indeed we need to override that 100/200sec condition if not in IBD.
This is important as it will slow the propagation of a block

dangershony pushed a commit that referenced this issue Sep 4, 2017
…ocks immediately #392 (#396)

* [BlockStoreLoop] Refactor the BlockStoreSteps so that it returns a enum result #330

* BlockStoreLoop] Refactor the BlockStoreSteps so that it returns a enum result #330

Review comments

* [BlockStoreLoop] Refactor the BlockStoreSteps so that it returns a enum result #330

Review

* [Improvement] Refactor BlockStorePuller/BlockStoreLoop so that BlockStoreInnerStepFindBlocks can ask for multiple blocks #339

Commit before merge

* Revert rename

* #361

Changes as per review

* [Improvement] Refactor BlockStorePuller/BlockStoreLoop so that BlockStoreInnerStepFindBlocks can ask for multiple blocks #339 #361

Removed from ShouldStopFindingBlocks

* [Improvement] Refactor BlockStorePuller/BlockStoreLoop so that BlockStoreInnerStepFindBlocks can ask for multiple blocks #339

Fixes as per review

* Refactored ProcesPendingStorageStep

* Added better logging

* Fixed bug

* Added comments to ProcessPendingStorageContext

* Split when in IBD and not in IBD

* Logic improvements

* Changes as per Dan's review
@fassadlr fassadlr closed this as completed Sep 5, 2017
codingupastorm pushed a commit to codingupastorm/StratisBitcoinFullNode that referenced this issue Jul 8, 2020
Adjust log levels in TokenlessKeyStoreManager
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants