op-node: Remove peer scores once the retain period is reached#5792
op-node: Remove peer scores once the retain period is reached#5792OptimismBot merged 3 commits intodevelopfrom
Conversation
Changes the base recordScore to act as if records have been pruned as soon as they are eligible rather than only if the GC has run.
|
✅ Deploy Preview for opstack-docs canceled.
|
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #5792 +/- ##
===========================================
- Coverage 42.28% 39.74% -2.54%
===========================================
Files 464 306 -158
Lines 30078 25425 -4653
Branches 876 0 -876
===========================================
- Hits 12717 10104 -2613
+ Misses 16361 14368 -1993
+ Partials 1000 953 -47
Flags with carried forward coverage won't be shown. Click here to find out more.
|
|
This PR has been added to the merge queue, and will be merged soon. |
|
This PR is next in line to be merged, and will be merged as soon as checks pass. |
1 similar comment
|
This PR is next in line to be merged, and will be merged as soon as checks pass. |
Description
Remove peer scores once the retain period is reached. This ensures that peers disconnected because their score dropped too low are able to connect again once the ban period expires. This also matches the score retention policy used by the gossip component where scores do not decay while the peer is connected, but are dropped entirely after the retention period expires.
Changes the base recordScore to act as if records have been pruned as soon as they are eligible rather than only if the GC has run.
Tests
Updated tests to cover this behaviour.
Metadata