You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It sounds like an interesting academic exercise, but I doubt it has much practical application in the real world (talking about the discussion in the blog). It shouldn't be too difficult to implement it in the current BQC.
If its a problem just at the queue level, use a separate container for each queue (or use the DirectMessageListenerContainer where different queues are processed on different threads).
Expected Behavior
if consumer detect Bad Queue, get rid of it while preserving Good Queue
Current Behavior
No action on Bad Queue and Good Queue
(It seems that there are only simple consumers)
Context
I would like to implement the CoDel algorithm in the existing BlockingQueueConsumer or create a new Consumer.
See Also
CoDel in wikiepdia
CoDel in RFC
CoDel in RabbitMQ's disscussion
CoDel in RabbitMQ's Blog
The text was updated successfully, but these errors were encountered: