Handling orphan queues

[arnauorriols]

(This is not an issue, but a general AMQP question that arises when using this exchange type)

This exchange is aimed at scaling not by having n consumers for a queue, but having 1 queue for consumer, and n queues.

This requires flexibility in adding or removing queues. For instance, if I add a new worker to my worker set, I will create a new queue, bind it to the consistent-hash exchange, and it will start to get its share of messages. Likewise, if I remove a new worker from my worker set, (for maintenance, because it crashed, downscaling...) I need my queue to be removed as well, otherwise it will fill up with messages that won't get consumed.

As you can imagine, ignoring the race condition in the routing mentioned, I must guarantee that "at most" all messages are processed by my workers. Do you have any suggestion on how to deal with the messages that might be inside the queue that I need deleted?

Thanks.

[michaelklishin]

Please post questions to rabbitmq-users or Stack Overflow. RabbitMQ uses GitHub issues for specific actionable items engineers can work on, not questions. Thank you.

[andrewmichaelsmith]

I'm also interested by this problem and have posted the q on stackoverflow: http://stackoverflow.com/questions/38872992/rabbitmq-scaling-queues-with-the-consistent-hash-exchange.