[rabbitmq-discuss] Newbie Q: Bugs in 2.8.2-1?
ebravick at springsemantics.com
Tue Jun 19 15:16:41 BST 2012
When 2.8.2 rolled, we also got snagged by this. It was actually a bit of a
mess for us. Like a lot of companies, we are lean on administrators (500+
servers per administrator) and fast moving. Rabbit is newer in our
infrastructure but its been really stable, so we had classified it as
"production safe" for both the application and its packaging. In our case,
we've re-classified the packaging as "development" meaning that when a new
version rolls, it has to be manually upgraded (sent through the QA process
to test for this sort of breakage.)
Its getting more and more common for our machines to have large memory
spaces, and more and more common that applications run almost entirely out
of memory. My guess is that others see the same trend upwards in memory
size... so this is probably something you'll continue to have more issues
with rather than less. Given that trend, I'd recommend that the packaging
check for this state (if upgrading from <2.8.2) and fail the upgrade if the
appropriate values aren't set (i.e. you'll end up with a failed Rabbit at
the end of the upgrade.) For people starting with 2.8.2+, you might
consider re-visiting the hard failure and making this a warning state
instead... seems to me there's a valid argument to throw a warning here
rather than blocking (however, I could be entirely incorrect about that.)
On Mon, Jun 18, 2012 at 4:08 PM, Matthias Radestock
<matthias at rabbitmq.com>wrote:
> On 18/06/12 20:22, Philip K. Warren wrote:
>> We have encountered issues in RabbitMQ 2.8.2 and greater with the
>> default 'disk_free_limit' monitoring. If you are running on a system
>> with more available RAM than disk space out of the box, RabbitMQ will
>> block consumers in its default configuration.
> We are surprised by how many people get caught out by that.
> Are there perhaps some popular Amazon EC2 images that are configured with
> very little disk space in /var/lib?
-- Eric Bravick, CTO
-- Spring Semantics, Inc.
-- 588 Sutter St. #232
-- San Francisco, CA 94102
-- Office = 415.906.3853
-- Email = ebravick at springsemantics.com
-- ebravick on Google+ and just about all Social Media
-- All Communications Legally Bound by this Agreement:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss