Update default configuration for revoked HTLC clean-up #3212
Conversation
This file contains hidden or 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
pm47
reviewed
Nov 14, 2025
This ensures that we don't have messages queuing up in the mailbox when the DB is busy.
t-bast
force-pushed
the
update-default-htlc-info-cleaner-cfg
branch
from
d054095 to
209c21e
Compare
pm47
approved these changes
Nov 18, 2025
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.
The default configuration for removing old rows containing revoked HTLC data after a channel close was too slow and inadequate for most nodes. We update it to use smaller batches without a much shorter interval.
Thanks @DerEwige for providing data about their experiments.
Fixes #3211