Quorum queue not FIFO

[Pieter van der Berg]

Hallo,

We use a quorum queue in a scenario where we have multiple publishers publishing to the same fanout exchange. The exchange puts the message in a quorum queue which is consumed by 1 consumer and a classis queue with ttl of 7 days with no consumers.

When the consumer goes offline and comes back and needs to catch up on the messages in the quorum queue it get's them delivered in random order. 

The cluster has tree nodes and we use the timestamp plugin to timestamp every messages entering the queue.

Any clue why messages aren't consumed FIFO?

Thx

[Henrik Peng]

It's because the broker thinks this is a new client when it reconnects to the queue thus the messages were delivered by round robin.

Thanks.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/9ad4d60a-9c9b-4560-a982-e07f2d40cfaan%40googlegroups.com.