I didn't realize this about queues. I thought that's where the state was in Rabbit. For example, I thought when a node goes down, the messages in the queues in that node are lost.�<br><br><div class="gmail_quote">On Mon, Apr 12, 2010 at 10:25 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@lshift.net">matthias@lshift.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Dan,<br>
<div class="im"><br>
Tony Garnock-Jones wrote:<br>
> Dan Di Spaltro wrote:<br>
>> Is there anyway you can specify a memory/disk/length limit to a queue<br>
</div>>> size with the action being a similar to a fixed window? [...]<br>
<div class="im">><br>
> It's not exactly on the roadmap, but it's something we've considered before.<br>
</div>> There are some questions that need careful thought though [...]<br>
<br>
One particular tricky issue is sharing. AMQP message may get delivered<br>
to 0, 1 or *several* queues. RabbitMQ generally only keeps *one* copy of<br>
a message, regardless of how many queues it ends up in. So queues end up<br>
sharing messages. And some data can even be shared *between* messages.<br>
<br>
Hence there really is no such thing as a per-queue memory/disk footprint.<br>
<br>
Furthermore, there is no way to determine the memory footprint of a<br>
message precisely due to memory fragmentation, gc, etc.<br>
<br>
<br>
Regards,<br>
<font color="#888888"><br>
Matthias.<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</div></div></blockquote></div><br>