[rabbitmq-discuss] Failed upgrade from 1.8.1 to 2.1.0
matthew at rabbitmq.com
Mon Oct 11 22:23:41 BST 2010
On Fri, Oct 08, 2010 at 11:53:28AM -0700, David King wrote:
> And as you can see in the memory graph I included at the end there,
> the bump at the end was this attempted upgrade, and the machine
> definitely didn't run out of RAM. But that "924 file handles" does
> look quite low, how can I increase that?
ulimit -n and /etc/security/limits.conf
However, for the number of queues you have, 924 is more than plenty.
The rest of your details leave me puzzled. Is there any possibility of
you being able to attempt the migration again, but without any consumers
at all? - literally just duplicate all your incoming streams into a new
Rabbit? - I'm curious if the queues will continue to fill correctly for
some time before exhausting RAM. Also, during this time, the output of
"rabbitmqctl list_queues name backing_queue_status" would be useful.
I remember when I was in your office we talking briefly about the
monitoring you were doing, but I've since forgotten - how are the stats
for those graphs being obtained? - is something just shelling out to
rabbitmqctl or is something else going on or...?
Your graphs that you posted didn't include the unacknowledged_messages
field which is available from rabbitmqctl list_queues, or from
rabbitmqctl list_channels. Do you have that data for that period of
More information about the rabbitmq-discuss