<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">From plugin's readme:<br>
<blockquote><tt>Each message gets delivered to at most one queue.
Normally, each
</tt><tt><br>
</tt><tt>
</tt>
<div class="parity1">
<tt><br>
</tt><tt>message gets delivered to exactly one queue, but
there is a race
</tt><tt><br>
</tt>
</div>
<tt>
</tt>
<div class="parity0">
<tt><br>
</tt><tt>between the determination of which queue to send a
message to, and the
</tt><tt><br>
</tt>
</div>
<tt>
</tt>
<div class="parity1">
<tt><br>
</tt><tt>deletion/death of that queue that does permit the
possibility of the
</tt><tt><br>
</tt>
</div>
<tt>
</tt>
<div class="parity0">
<tt><br>
</tt><tt>message being sent to a queue which then disappears
before the message
</tt><tt><br>
</tt>
</div>
<tt>
</tt><tt>
</tt><tt><br>
</tt><tt>is processed. Hence in general, at most one queue.<br>
</tt></blockquote>
<tt>Note that consistent-hashing does not ensure persistence of
messages due this issue.<br>
<br>
In my experience consistent-hashing handles bindings removal or
queue deletions<br>
poorly. I had been running into NO ROUTE exception constantly
when I used <br>
consistent-hashing-exchange with auto-deleted queues.<br>
<br>
I also tried to use alternate-exchanges to catch bad cases. Had
difficulties <br>
with that also.<br>
<br>
</tt>On 01/16/2013 01:21 PM, Grégoire Seux wrote:<br>
</div>
<blockquote
cite="mid:CAE3ghBvo-EOQXG8s8Tr0AS2yd1QU4trD8+ThEk1Pbj44998z=w@mail.gmail.com"
type="cite">
<pre wrap="">1. create a consistent hashing exchange (auto-delete, non durable),
start send messages with random routing key
2. create a queue (non durable, exlusive, auto delete) and bind it to
the exchange (routing key : "20"), consume messages from it
3. delete the queue</pre>
</blockquote>
<br>
</body>
</html>