Dear RabbitMQ members,<br><br>We're testing a two nodes cluster running RabbitMQ (2.6.1) and we don't understand the cluster benefits beyond having a shared knowledge about the metadata, as queues are sticky to the node upon which they are created, queues are limited to node's hardware capabilities (CPU, Memory, Disk, ...). Can you explain us the cluster benefits? After adding another node to the cluster, is there any way to rebalance the existing queues among all nodes? <br>
<br>We're planning to set up about 30.000 queues and 100.000.000 messages with an average of 1 Kb each, every time a message is consumed it reenters the corresponding queue until it's deleted. What do you think?<br>
<br>Looking forward to hearing from you.<br><br clear="all"><br>-- <br>Guillem Anguera<br><a href="mailto:guillem@trovit.com" target="_blank">guillem@trovit.com</a><br>Tel: 686.528.792<br><br><img src="http://www.trovit.com/content/trovit.png" height="46" width="96"><br>
<a href="http://www.trovit.com" target="_blank"></a><a href="http://www.trovit.com" target="_blank">www.trovit.com</a><br>Your partner for qualified users <br>