Duplicate key errors in EthScheduler-Transactions #5824
Labels
snack
Smaller coding task - less than a day for an experienced dev
TeamChupa
GH issues worked on by Chupacabara Team
TeamGroot
GH issues worked on by Groot Team
TeamRevenant
GH issues worked on by Revenant Team
Description
As a node operator, I want
ERROR
level messages in the logs only to apply to important or actionable situations.The below errors and stack traces don't seem to be useful, and as a node operator there doesn't seem to be anything I can do in response to them. Since Besu apparently keeps running fine, they should probably be demoted to
DEBUG
.Acceptance Criteria
ERROR
level messages that are not useful are suppressed.Steps to Reproduce (Bug)
Run Besu for a while.
Expected behavior:
Logs don't contain unhelpful
ERROR
level stack traces.Actual behavior: [What actually happens]
Frequency: [What percentage of the time does it occur?]
A couple of times per hour.
Versions (Add all that apply)
Additional Information (Add any of the following or anything else that may be relevant)
I am running with the
Xlayered-tx-pool=true
flag.The text was updated successfully, but these errors were encountered: