[rabbitmq-discuss] How to handle extremely large queues
greg.poirier at opower.com
Sun Feb 16 19:57:37 GMT 2014
If Rabbit inaccurately reports the amount of memory it's using, how are we
to provision systems? With some understanding of normal load, however
suboptimal the use case may be, we should have an understanding of memory
requirements... Particularly when rabbit provided a reporting mechanism to
confirm out expected memory usage.
I guess I am confused.
On Sunday, February 16, 2014, Alvaro Videla <videlalvaro at gmail.com> wrote:
> Keep in mind that there's small memory footprint per message, even if
> the message has been paged to disk.
> > They are many small messages. Each node in the cluster has 8 gigs but is
> > only using maybe 2. Is memory really the problem?
> > On Sunday, February 16, 2014, Michael Klishin <
> > wrote:
> >>> In our current configuration, we have a 3-node cluster with 2 disc and
> >>> ram node with HA mirroring to all nodes in the cluster. In periods of
> >>> utilization of the cluster, we are noticing frequent partitioning. We
> >>> narrowed it down to this particular use case as none of our other
> >>> (running on the same physical hardware with the same cluster
> >>> experience this kind of partitioning.
> >>> Is there some better way that we can configure RabbitMQ to handle this
> >>> kind of load pattern? I understand this is perhaps not the best way to
> >>> RabbitMQ, but it is unavoidable for the time being. Any suggestions
> would be
> >>> appreciated.
> >> Short answer is: give it more RAM.
> >> Relevant blog posts:
> >> --
> >> MK
> >> http://github.com/michaelklishin
> >> http://twitter.com/michaelklishin
> > _______________________________________________
> > rabbitmq-discuss mailing list
> > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> rabbitmq-discuss mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss