[rabbitmq-discuss] Confirm consistent hash exchange behavior
steveolivier22 at gmail.com
Thu Mar 14 17:07:56 GMT 2013
I wanted to get some clarification on CHX hash key routing to a queue. Let's
say I have Queue1 and Queue2 bound with equal weight to a CHX. I produce a
message with the routing key "Car.Color.Blue" to the CHX and it is routed to
Queue2. All is well. I delete Queue2. I produce another message with the
routing key "Car.Color.Blue" to the CHX and it is now routed to Queue1. All
is well. I re-create and bind Queue2 to the CHX. I produce another message
with the routing key "Car.Color.Blue" to the CHX and it is routed back to
Queue2. That's the part that seemed odd.
The design requirements I have is that all messages with the same
routing-key be present in only one queue. I can't meet those requirements by
that queue deletion/re-creation with the same name. So, I'd have to avoid
doing that or find out if this is expected behavior.
The set up I have is this...
P ---> TopicExchange --->CHX ---> Q1, Q2
Producers send messages with routing keys like "Car.Color.<some color>".
The CHX is bound to the TopicExchange with a routing key of "Car.Color.#".
Queues 1 and 2 are bound to the CHX with equal weight.
I am at Rabbit 3.0.1.
View this message in context: http://rabbitmq.1065348.n5.nabble.com/Confirm-consistent-hash-exchange-behavior-tp25458.html
Sent from the RabbitMQ mailing list archive at Nabble.com.
More information about the rabbitmq-discuss