WARN: The low priority inbound consensus queue is full!
jeremiasbaur opened this issue · 5 comments
Hello,
I am currently facing the problem with this warning message:
2021-02-04T10:11:02.922389150Z: WARN: The low priority inbound consensus queue is full!
2021-02-04T10:11:02.922998155Z: WARN: The low priority inbound consensus queue is full!
2021-02-04T10:11:02.923671724Z: WARN: The low priority inbound consensus queue is full!
2021-02-04T10:11:02.924406857Z: WARN: The low priority inbound consensus queue is full!
2021-02-04T10:11:02.925107106Z: WARN: The low priority inbound consensus queue is full!
2021-02-04T10:11:02.925777760Z: WARN: The low priority inbound consensus queue is full!
2021-02-04T10:11:02.926401698Z: WARN: The low priority inbound consensus queue is full!
2021-02-04T10:11:02.927041256Z: WARN: The low priority inbound consensus queue is full!
2021-02-04T10:11:02.927670285Z: WARN: The low priority inbound consensus queue is full!
How can I resolve this? My node becomes unusable because this spam of logs slows it down.
@jeremiasbaur: We are currently, and for the past few hours, seeing a large number of transactions being transmitted on the network. The warning indicates that your node is receiving transactions faster than it can process them, so it is dropping some of them. Your node is slowed down by that high transaction load, you cannot resolved the situation unfortunately.
Important addition: The node is working as expected under such a high load.
Sorry, I can't run my node and complete the challenges at the moment. It takes ages to just send one transaction.
Why do you think that there are currently a large number of transaction being transmitted? The blocks show very few transactions. There were way more transactions in the blocks 2-7 days ago.
We still don't have the full view of what is going on on the network and why. Most of the spamming transactions seem to be invalid. There are many reasons a transaction can be invalid and only few kinds show up in the block explorer (e.g. not sufficient transaction fee). So the block explorer seems empty but the nodes have to handle a high load. In scope of the transaction challenges, there were realistically many transactions in each block, most of them valid, and the network was performing just fine.
Don't worry about the transaction challenges. Even though it is not stated explicitly, the 7 days with transactions do not have to be consecutive. Meaning, it's 7 single days, not a week. The submission deadline is first on 17-02.
We have an update available. Please follow our instructions on the status page and the Medium post.