[rabbitmq-discuss] Can RabbitMQ handle big messages?

Zabrane Mickael zabrane3 at gmail.com
Mon Mar 12 15:42:52 GMT 2012

It's not a bug. You have to be aware of it to build reliable systems in case of multiple connected Erlang nodes.


On Mar 12, 2012, at 4:31 PM, Tony Garnock-Jones wrote:

> On 12 March 2012 08:51, Irmo Manie <irmo.manie at gmail.com> wrote:
> Clustered nodes are connected via 1 tcp connection, which must also
> transport a (erlang) heartbeat. If your big message takes more time to
> transfer between nodes than the heartbeat timeout (anywhere between
> ~20-45 seconds if I'm correct), the cluster will break and your
> message is lost.
> Wow! Is that really the case? Erlang's distribution breaks if no heartbeats have been received *even if there's traffic coming in on the wire*? Sounds like an Erlang bug. Or perhaps there's some subtlety in the design I'm not seeing!
> Regards,
>   Tony
> -- 
> Tony Garnock-Jones
> tonygarnockjones at gmail.com
> http://homepages.kcbbs.gen.nz/tonyg/
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120312/7ecfbc8b/attachment.htm>

More information about the rabbitmq-discuss mailing list