fix: set recent reject db log file limit to 10 #3681
Merged
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.
What problem does this PR solve?
In this PR, we introduce the recent reject DB to record recently rejected transactions, which is implemented as rocksdb with TTL, using the default DB parameter configuration.
Since then, this db has been very heavily used on my machine until now:
dust -n 50 -d 1 4.0K ┌── logs 8.0K ├── ancient 212K ├── tmp 2.8M ├── network 164M ├── indexer 1.5G ├── tx_pool 24G ├── db 26G ┌─┴ .
However, the data inside is actually all
LOG.old.xxx
logs.As a TTL database, its data storage is inherently time-limited, and it is obviously not reasonable to keep so many DB logs by default.
By default, rocksdb keeps 1000 log files, which is too heavy for this DB, so this PR will change the default value to 10
Check List
Tests
Release note