Thanks Emile,<div><br></div><div>If there is only one broker and number of clients increase, how well will it scale? Do you think after a certain level RabbitMQ broker will become a bottleneck?</div><div><br></div><div>Is it possible to have backup RabbitMQ brokers so if the original one goes down, back-up becomes active?</div>
<div><br></div><div>Thanks,</div><div>Nabeel<br><br><div class="gmail_quote">On Wed, Apr 25, 2012 at 9:43 PM, Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Nabeel,<br>
<br>
On 25/04/12 14:11, Nabeel Akhtar wrote:<br>
> If I want to collect logs from multiple machines, would I need to run<br>
> RabbitMQ broker on all machines, or just one? If I run it on just one<br>
> machine, then which component should I run on all nodes?<br>
<br>
You only need one broker. You will need a RabbitMQ client, or some<br>
software that can speak a suitable protocol (such as STOMP) on all<br>
machines that produce logs.<br>
<br>
This post by Peter Ledbrook has some background that you may find useful:<br>
<a href="http://blog.cloudfoundry.com/post/13481011156/rethink-application-logging-with-rabbitmq" target="_blank">http://blog.cloudfoundry.com/post/13481011156/rethink-application-logging-with-rabbitmq</a><br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
-Emile<br>
<br>
<br>
</font></span></blockquote></div><br></div>