4 ms·
One solution which we did was to use the official delay plugin provided by the Rabbit MQ. It’s working good, so far https://www.rabbitmq.com/blog/2015/04/16/sc
by avinassh 6y ago
One solution which we did was to use the official delay plugin provided by the Rabbit MQ. It’s working good, so far
https://www.rabbitmq.com/blog/2015/04/16/scheduling-messages-with-rabbitmq/ https://www.rabbitmq.com/blog/2015/04/16/scheduling-messages...
- zbentley 6y agoAwesome! I was peripherally aware of that, I think, but had filed it as "not ready" for some reason. Will definitely give it another look, thanks!
- hnrodey 6y agoHopefully you're aware of some of the shortcomings of this plugin when operating in a multi-node cluster. The plugin keeps a node-specific database of the messages that are to be delayed. If the node is unavailable or lost, so too are the messages the node was keeping for future publish. Also, there is no visibility in to the messages that are awaiting delay. 10? 100? 5000? Your guess is as good as mine and you'll never be able to figure out what's in to-be-published pipeline. Signed, someone who has dealt with these issues.
- hnrodey 6y agoHopefully you're aware of some of the shortcomings of this plugin when operating in a multi-node cluster. The plugin keeps a node-specific database of the messages that are to be delayed. If the node is unavailable or lost, so too are the messages the node was keeping for future publish. Also, there is no visibility in to the messages that are awaiting delay. 10? 100? 5000? Your guess is as good as mine and you'll never be able to figure out what's in to-be-published pipeline. Signed, someone who has dealt with these issues.