-
Notifications
You must be signed in to change notification settings - Fork 634
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled QueueFull exception #1032
Labels
Comments
This was referenced Jul 17, 2018
gsalgado
added a commit
to gsalgado/py-evm
that referenced
this issue
Jul 20, 2018
* Renamed to PeerSubscriber because that's what it really is * New @AbstractMethod max_queue_size, to force each subscriber to define their own * Peer now keeps a list of actual PeerSubscribers instead of just their msg queues * PeerSubscriber provides APIs to add msgs to queue and check queue size, abstracting underlying implementation * If an attempt is made to add a msg but the queue is full, we log a warning and drop the msg (Closes: ethereum#1032)
gsalgado
added a commit
to gsalgado/py-evm
that referenced
this issue
Jul 20, 2018
* Renamed to PeerSubscriber because that's what it really is * New @AbstractMethod max_queue_size, to force each subscriber to define their own * Peer now keeps a list of actual PeerSubscribers instead of just their msg queues * PeerSubscriber provides APIs to add msgs to queue and check queue size, abstracting underlying implementation * If an attempt is made to add a msg but the queue is full, we log a warning and drop the msg (Closes: ethereum#1032)
gsalgado
added a commit
to gsalgado/py-evm
that referenced
this issue
Jul 20, 2018
* Renamed to PeerSubscriber because that's what it really is * New @AbstractMethod max_queue_size, to force each subscriber to define their own * Peer now keeps a list of actual PeerSubscribers instead of just their msg queues * PeerSubscriber provides APIs to add msgs to queue and check queue size, abstracting underlying implementation * If an attempt is made to add a msg but the queue is full, we log a warning and drop the msg (Closes: ethereum#1032)
gsalgado
added a commit
that referenced
this issue
Jul 21, 2018
* Renamed to PeerSubscriber because that's what it really is * New @AbstractMethod max_queue_size, to force each subscriber to define their own * Peer now keeps a list of actual PeerSubscribers instead of just their msg queues * PeerSubscriber provides APIs to add msgs to queue and check queue size, abstracting underlying implementation * If an attempt is made to add a msg but the queue is full, we log a warning and drop the msg (Closes: #1032)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is wrong?
I've seen this a few times today while running a full node on mainnet.
I believe it's the TxPool that is not consuming the messages fast enough, because when that happened the chain syncer was requesting blocks and processing them just fine
How can it be fixed
Need to investigate
The text was updated successfully, but these errors were encountered: