[rabbitmq-discuss] RabbitMQ / Erlang not running on all cores?

Michael Klishin mklishin at gopivotal.com
Tue Oct 22 23:47:10 BST 2013

On 23 Oct 2013, at 02:38, Matt Pietrek <mpietrek at skytap.com> wrote:

> Regarding the suggestion of "RABBITMQ_ALLOW_INPUT=true", this is a bit tricky for me to run. For starters, this is a Rabbit instance running in a production environment so I can't easily restart it. And even if I could, the way we start RabbitMQ is a bit quirky (long story).

I definitely was not suggesting that you run your production node with RABBITMQ_ALLOW_INPUT. 

You can start
a separate node on the same machine just for a moment, with RABBITMQ_ALLOW_INPUT and RABBITMQ_PORT
overridden. If you run management plugin or other plugins that listen on ports, then you'll need to use a separate config.


If you start RabbitMQ in an unusual way, can it be that you modify `erl` arguments,
in particular +A?


More information about the rabbitmq-discuss mailing list