fix: stores: Tune down StorageDeclareSector` log-lvl #11045
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.
Related Issues
Closes: #10901
Proposed Changes
Tune down the log-level on
StorageDeclareSector
to debug.Additional Info
Boost added an index integrity check in Boost 1.7.0 which causes users to see logs like these more often:
The WARN level here seems wrong as these are expected, and the interval of how often this gets called can be tuned in the configs on Boost.
I have added a KB-article explaining why users might see these logs as well here: https://lotus.filecoin.io/kb/redeclared-sector-log/
Checklist
Before you mark the PR ready for review, please make sure that:
<PR type>: <area>: <change being made>
fix: mempool: Introduce a cache for valid signatures
PR type
: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, testarea
, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps