<div class="gmail_quote">Thanks for the reply --</div><div class="gmail_quote"><br></div><div class="gmail_quote">On Sun, Mar 27, 2011 at 9:38 PM, Jerry Kuch <span dir="ltr"><<a href="mailto:jerryk@vmware.com">jerryk@vmware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">150 is a pretty big sounding cluster... Out of curiosity, what's motivating you to go so big (if you don't mind saying)?<br>
</blockquote><div><br></div><div>I am doing a QoS analysis of publish-subscribe overlays using RabbitMQ in wide area networks (These are country wide networks, so even a 1000 nodes might be insufficient :-)) So stuff like packet delay, loss, out-of-order delivery etc.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On that note, because RabbitMQ clustering is based on Erlang distribution, the current practical limit you'll probably run up against is somewhat lower than the 150 you have in mind. Something more like 32 to 64.<br>
</blockquote><div><br></div><div>Is there a configuration that would let me scale to >64 nodes, even if it would not be practical? And in case Erlang does not scale well, I'll probably have to resort to entirely another middleware -- any suggestions that would work on a larger number of nodes?</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
If you can say more about your goals it's likely that someone on the Rabbit team can suggest something helpful.<br></blockquote><div><br></div><div>The analysis I'm carrying out on >100 nodes is actually on a single system. These 'nodes' are actually many light weight linux containers (more or less virtual machines) connected by a simulated NS3 network topology. But I doubt this would be the cause of the clustering problem, as <50 nodes were clustering without any difficulty.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br><div><div class="h5">
On Mar 26, 2011, at 10:32 PM, "Advait Alai" <<a href="mailto:advaitalai@gmail.com">advaitalai@gmail.com</a>> wrote:<br>
<br>
> Hi,<br>
><br>
> I'm trying to add 150 nodes to a RabbitMQ cluster. After around 50 nodes, the stop-reset-cluster-start iteration starts giving the error:<br>
><br>
> Stopping node rabbit@node130 ...<br>
> ...done.<br>
> Resetting node rabbit@node130 ...<br>
> ...done.<br>
> Clustering node rabbit@node130 with [rabbit@node117] ...<br>
> ...done.<br>
> Starting node rabbit@node130 ...<br>
> Error: {cannot_start_application,rabbit,<br>
> {bad_return,<br>
> {{rabbit,start,[normal,[]]},<br>
> {'EXIT',{rabbit,failure_during_boot}}}}}<br>
><br>
> Note that I am sequentially adding nodes to build a cluster (as an initialization step) before creating any queues/exchanges or running any amqp script.<br>
><br>
> How do I solve this problem? Is it because RabbitMQ imposes a hard cluster size limit?<br>
><br>
> Also, does RabbitMQ scale well to around 1000 nodes?<br>
><br>
> Thanks<br>
</div></div>> _______________________________________________<br>
> rabbitmq-discuss mailing list<br>
> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
> <a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br>