fix(mempool): change "mempool is full" log level to debug (backport #4123)#4144
Merged
mergify[bot] merged 3 commits intov1.xfrom Sep 20, 2024
Merged
fix(mempool): change "mempool is full" log level to debug (backport #4123)#4144mergify[bot] merged 3 commits intov1.xfrom
mergify[bot] merged 3 commits intov1.xfrom
Conversation
it happens in benchmark or production when traffic is high, the log frequency is very high because it's triggered by p2p tx propagation message. Solution: - change it to debug level --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit 1323b1c) # Conflicts: # mempool/reactor.go
Contributor
Author
|
Cherry-pick of 1323b1c has failed: To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
it happens in benchmark or production when traffic is high, the log frequency is very high because it's triggered by p2p tx propagation message.
Solution:
This is an automatic backport of pull request #4123 done by [Mergify](https://mergify.com).