|
|
| Author |
Message |
|
| Guest |
 Posted: Tue Sep 15, 2009 3:57 pm |
 |
|
|
Guest
|
queue's are marked as durable and persistent on both sides:
Producer:
send_message(Channel, Ticket, X, RoutingKey, Payload) ->
|
|
|
| Back to top |
|
| Guest |
| Posted: Tue Sep 15, 2009 4:04 pm |
|
|
|
Guest
|
Doing some investigation into what happened, apparently the memory just instantly got used, it wasn't leaking something slowly...any ideas?
Attached is an image of memory usage, then the consumer dies freeing up the memory used later.
On Tue, Sep 15, 2009 at 8:56 AM, Suhail Doshi <suhail@mixpanel.com (suhail@mixpanel.com)> wrote:
Quote: queue's are marked as durable and persistent on both sides:
Producer:
send_message(Channel, Ticket, X, RoutingKey, Payload) ->
|
|
|
| Back to top |
|
| Guest |
| Posted: Wed Sep 16, 2009 11:49 am |
|
|
|
Guest
|
On Tue, Sep 15, 2009 at 17:03, Suhail Doshi <suhail@mixpanel.com> wrote:
> Doing some investigation into what happened, apparently the memory just
> instantly got used, it wasn't leaking something slowly...any ideas?
> Attached is an image of memory usage, then the consumer dies freeing up the
> memory used later.
It looks like erlang was trying to allocate 5 gigs of RAM, and failed.
This could have happened during garbage collection, but only
if a single erlang process was using all the memory.
Do you have a single large queue?
Are you sure that the queue had reasonable size during the crash?
Maybe all the consumers had died and rabbit just ran out of memory?
Cheers!
Marek Majkowski
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Sep 17, 2009 4:47 pm |
|
|
|
Guest
|
On Wed, Sep 16, 2009 at 4:48 AM, majek04 <majek04@gmail.com (majek04@gmail.com)> wrote:
Quote: On Tue, Sep 15, 2009 at 17:03, Suhail Doshi <suhail@mixpanel.com (suhail@mixpanel.com)> wrote:
> Doing some investigation into what happened, apparently the memory just
> instantly got used, it wasn't leaking something slowly...any ideas?
> Attached is an image of memory usage, then the consumer dies freeing up the
> memory used later.
It looks like erlang was trying to allocate 5 gigs of RAM, and failed.
This could have happened during garbage collection, but only
if a single erlang process was using all the memory.
Do you have a single large queue?
Yes just 1 queue, definitely adds up after a while if consumers are not running
|
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
