The linked documentation comes out ao .7 for a t2.large
We can also prevent rabbit from going to disk until more memory
is full, but that isn't needed right now.

Rabbit's logs go to /var/log/rabbitmq/ these files are our internal
queue monitoring logs and they will be recreated by
/edx/app/rabbitmq/log-rabbitmq-queues.sh

Without this, we end up with > 10K empty files which makes logrotate and
splunk sad.

Right now these files never go away, and some are a million lines long.
This means splunk eats all the disk IO if we ever restart.

This method relied on the `hostvars` variable provided by ansible to always
be all the nodes in the rabbitmq cluster.  The hostvars var broke as a result
of the upgrade to ansible 1.9 but also even if it did work, this method
required that you always run rabbit plays on the whole cluster.  This is not
reasonable as it makes it very hard to heal a single node that may have fallen
over.

From here on, the RABBITMQ_CLUSTERED_HOSTS var should be used instead to
specify the rabbit hosts that are part of a cluster.

Alsa, add connection logging to rabbitmq.