Change getNodeFat Missing Node State Tree error into warning #5455
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.
High Level Overview of Change
TaggedCache
(i.e.LedgerHistory
,TreeNodeCache
,AcceptedLedgerCache
and a few more).TaggedCache
can have different expiry thresholds.processLedgerRequest
triggers getLedger, which checksLedgerHistory
LedgerHistory
, then ledger contents is also preserved in the other cache -TreeNodeCache
.TreeNodeCache
can be calculated differently, it could have been already removed from memory by the sweep function.p.s. Ordering in the
Application::doSweep
is done correctly in this case (firstTreeNodeCache
, second -LedgerHistory
), but this does not help because of the difference in the sweep expiry time.Context of Change
Change the Log level to warning and monitor its frequency. If we start seeing frequent occurrences of this event, this might indicate that the target age should be increased.
Type of Change
.gitignore
, formatting, dropping support for older tooling)API Impact
libxrpl
change (any change that may affectlibxrpl
or dependents oflibxrpl
)