pruning CLI flag was changed #27
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
added 2 commits
March 31, 2023 11:33
Signed-off-by: kogeler <roman.gavrilov@parity.io>
Signed-off-by: kogeler <roman.gavrilov@parity.io>
kogeler
requested review from
aardbol,
PierreBesson and
BulatSaif
and removed request for
aardbol
bakhtin
approved these changes
Mar 31, 2023
BulatSaif
reviewed
Mar 31, 2023
BulatSaif
approved these changes
Mar 31, 2023
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.
Changes:
the
--pruningCLI flag was renamedAlso, we meet the
WARN main state-db: Large pruning window of 3700 detected! THIS CAN LEAD TO HIGH MEMORY USAGE AND CRASHES. Reduce the pruning window or switch your database to paritydb.log warning. We should use a value like 256 for the state pruning mode. It's the default value according to the documentationthe
paritydbCLI flag was renamed. paritydb isn't an experimental feature anymorethe issues 22 was fixed completely
network timeouts were increased for the slow network case
molecule scenarios were fixed