Hi Marek,<br><br>For POC it worked, but we know that since ours is a "cloud" based application, it will scale. So we have to chose a broker carefully. Do we have a workaround for this ?<br><br>Regards,<br>Kshitiz Garg<br>
HP R&D Division<br><br>
<div class="gmail_quote">
On Mon, Nov 29, 2010 at 3:49 PM, Marek Majkowski <span dir="ltr"><<a href="mailto:majek04@gmail.com" target="_blank">majek04@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi,<br>
<br>
You have a valid point, just a quick question...<br>
<div><div></div><div><br>
On Mon, Nov 29, 2010 at 07:18, Kshitiz Garg <<a href="mailto:stephanion2002@gmail.com" target="_blank">stephanion2002@gmail.com</a>> wrote:<br>
> Hi Gustavo,<br>
><br>
> Sorry for replying late,<br>
><br>
> We don't have any figure yet, but on our pub-sub system, millions of of<br>
> publishers will be publishing messages.<br>
><br>
> Our system is as follows:<br>
><br>
> 1. A publisher publishes message on our rest APIs.<br>
> 2. From there, we first store those messages in DB.<br>
> 3. After storing, we publish the message on RabbitMQ setup using a load<br>
> balancer.<br>
> 4. Behind the load balancer, we have a cluster of 4 rabbitMQ nodes.<br>
> 5. At the consuming end, we have perl and java consumers fetching messages.<br>
> 7. These internal consumers send messages to the subscribers as per the<br>
> subscription protocol.<br>
><br>
> Now, if we add 4 RabbitMQ nodes in a cluster, all the credentials, exchanges<br>
> and bindings get copied to each mnesia db. However, since the queues are<br>
> specific to nodes, the message directed to a particular queue will be lost<br>
> (if the node on which that queue was created is down). This seems to be a<br>
> weak link for a scalable and High availability solution we need. Will the<br>
> message be persisted somewhere and delivered to that queue after that<br>
> particular node comes up?<br>
><br>
> If the message is gonna lost, can we have a workaround that we create copies<br>
> of the queues explicitly on each node. Now since they are copies, the<br>
> exchange will send the message to all the nodes and even if a node is down,<br>
> message will be delivered to all the copies of that queue.<br>
><br>
> We know that Clustering!=HA, but we do need Clustering with HA. Here since<br>
> even after clustering of 4 rabbitMQ nodes, the active-passive setup for each<br>
> of these 4 nodes becomes the bottleneck because of the complexity of the<br>
> non-replication of "queues". Is there any workaround or any other setup u<br>
> can suggest ?<br>
<br>
</div></div>... have you actually tried a setup with only a single RabbitMQ node, and did<br>
it really became a bottleneck?<br>
<font color="#888888"><br>
Marek<br>
</font><div><div></div><div><br>
<br>
> Regards,<br>
> Kshitiz Garg<br>
><br>
> On Sun, Nov 28, 2010 at 10:01 PM, Gustavo Aquino <<a href="mailto:aquino.gustavo@gmail.com" target="_blank">aquino.gustavo@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Hi Garg,<br>
>> Could you give to us more details about what you need? eg. it's messages<br>
>> throughput is per second? and etc.<br>
>> Regards.<br>
>><br>
>><br>
>><br>
>> On Wed, Nov 24, 2010 at 10:35 AM, Kshitiz Garg <<a href="mailto:stephanion2002@gmail.com" target="_blank">stephanion2002@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> Hi,<br>
>>><br>
>>> Can someone present a pictorial representation of 4-5 Rabbit MQ nodes<br>
>>> with Clustering and HA (it can also go on the RabbitMQ site). I wanted to<br>
>>> know about a RabbitMQ setup which is able to handle millions of messages.<br>
>>><br>
>>> I hope there would be many more users with such a requirement.<br>
>>><br>
>>> Thanks<br>
>>> Kshitiz Garg<br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> rabbitmq-discuss mailing list<br>
>>> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">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>
>>><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> rabbitmq-discuss mailing list<br>
> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">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>
><br>
><br>
</div></div></blockquote></div><br>