[rabbitmq-discuss] Disabling channel.flow
matthew at lshift.net
Mon Feb 1 17:23:44 GMT 2010
On Mon, Feb 01, 2010 at 10:43:44PM +0530, Rajkumar S wrote:
> On Mon, Feb 1, 2010 at 3:47 PM, Matthew Sackman <matthew at lshift.net> wrote:
> > Which version of Rabbit are you using? - the details for disabling
> > memory monitoring have changed between 1.7.0 and 1.7.1.
> I downloaded rabbitmq-public-umbrella using hg, the tip points to:
> changeset: 44:259da26ec626
> tag: tip
> parent: 43:0d8d8a6dddae
> parent: 42:b08e26cc7170
> user: David Wragg <dpw at lshift.net>
> date: Mon Oct 05 13:03:37 2009 +0100
> summary: Merge bug21745 into default
> I used hg to install stomp plugin also along with rabbit. I can always
> try and install latest/other versions if that helps.
You should *never* use tip. Tip is one of the daftest features of hg and
just points to the most recent commit. Given that we do branch per bug,
you could simply get *any* currently active branch.
There are later revisions than this. I would recommend you pull and hg
up -C default.
What you've actually given is the revision under
rabbitmq-public-umbrella. I should have been more clear: I was asking
for which version of rabbitmq-server are you using? However, I assume
you're building from source, in which case the details at
http://www.rabbitmq.com/extensions.html#memsup should help.
> I understand, but the flow control keeps hitting frequently enough to
> make rabbit-stomp almost useless :( So far I have not been able to
> exercise any sort of control over when the flow control kicks in. Is
> it possible to know how much memory rabbit thinks it has and how much
> more memory it can use before flow control kicks in?
Yes. In the logs, at start up you should see a message like:
=INFO REPORT==== 1-Feb-2010::13:36:41 ===
Memory limit set to 3151MB.
This is controlled by the vm_memory_high_watermark parameter which is
documented in the link above. When the Erlang VM has allocated more than
this amount of RAM, flow control will be invoked. If you set the
parameter to 0, then Rabbit will not monitor memory, nor will flow
control be used.
More information about the rabbitmq-discuss