Queue overflow error, change MAX_QUEUE_SIZE value
See original GitHub issueMy code:
# callback
def process_message_price(msg):
print(msg)
# websocket
bm = ThreadedWebsocketManager()
bm.start()
# listOfPairings: all pairs with USDT (over 250 items in list)
for pairing in listOfPairings:
conn_key = bm.start_trade_socket(callback=process_message_price,symbol=pairing)
bm.join()
hovewer after shor time, i am getting following error: ‘e’: ‘error’, ‘m’: ‘Queue overflow. Message not filled’
which is caused by MAX_QUEUE_SIZE in streams.py being too small for my program
How can i change this value outside of streams.py file ?
Thx
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:20
Top Results From Across the Web
How maxQueueSize and queueSizeRejectionThreshold work ...
According to my interpretation, if a server is not able to serve a request, then the clients will store the thread in the...
Read more >nginx - FreeBSD Listen Queue Overflows - can't increase max ...
For such environments, it is recommended to increase this value to 1024 or higher. The service daemon may itself limit the listen queue...
Read more >Is there a way to increase the maxQueueSize for Syslog output?
Hello Splunkers, I would like to know if there is any way to increase the queue of my syslog group. I mean, currently...
Read more >"Message queue is full" causes Foglight Agent Manager ...
To fix this, please increase the upstream max-disk-space setting for this agent manager. Cause. Max disk space is set to low value and...
Read more >Playing with Hystrix Thread Pool - Medium
When value is -1, a SynchronousQueue is used instead, a simple ... the maxQueueSize, only takes effect when maxQueueSize value is positive.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I was just playing around with the documentation code and got this same error when I was manually using the Asynchronous context manager.
What sorted it out for me was once you open the connection, you recieve the message you should close the context manager Here is my code:
Its the line
await socket.__aexit__(None, None, None)that sorted out the issue for meAnd put MAX_QUEUE_SIZE = 10000 There is no other way to fix this error I have no more than 10-15 restarts of the web socket on all USDT pairs per day (while the restart occurs within 5-7 seconds after the error)
Calling the restart of the stream from except did not work for me either, only in the function as a separate thread