Description of RabbitMQ configuration options
Configuration option = Default value Description
[oslo_messaging_rabbit]
= False (BoolOpt) Auto-delete queues in AMQP.
= False (BoolOpt) Use durable queues in AMQP.
= False (BoolOpt) Deprecated, use rpc_backend=kombu+memory or rpc_backend=fake
= 2 (IntOpt) How often times during the heartbeat_timeout_threshold we check the heartbeat.
= 60 (IntOpt) Number of seconds after which the Rabbit broker is considered down if heartbeat's keep-alive fails (0 disable the heartbeat). EXPERIMENTAL
= 1.0 (FloatOpt) How long to wait before reconnecting in response to an AMQP consumer cancel notification.
= 60 (IntOpt) How long to wait before considering a reconnect attempt to have failed. This value should not be longer than rpc_response_timeout.
= (StrOpt) SSL certification authority file (valid only if SSL enabled).
= (StrOpt) SSL cert file (valid only if SSL enabled).
= (StrOpt) SSL key file (valid only if SSL enabled).
= (StrOpt) SSL version to use (valid only if SSL enabled). Valid values are TLSv1 and SSLv23. SSLv2, SSLv3, TLSv1_1, and TLSv1_2 may be available on some distributions.
= False (BoolOpt) Use HA queues in RabbitMQ (x-ha-policy: all). If you change this option, you must wipe the RabbitMQ database.
= localhost (StrOpt) The RabbitMQ broker address where a single node is used.
= $rabbit_host:$rabbit_port (ListOpt) RabbitMQ HA cluster host:port pairs.
= AMQPLAIN (StrOpt) The RabbitMQ login method.
= 0 (IntOpt) Maximum number of RabbitMQ connection retries. Default is 0 (infinite retry count).
= guest (StrOpt) The RabbitMQ password.
= 5672 (IntOpt) The RabbitMQ broker port where a single node is used.
= 2 (IntOpt) How long to backoff for between retries when connecting to RabbitMQ.
= 1 (IntOpt) How frequently to retry connecting with RabbitMQ.
= False (BoolOpt) Connect over SSL for RabbitMQ.
= guest (StrOpt) The RabbitMQ userid.
= / (StrOpt) The RabbitMQ virtual host.
= False (BoolOpt) Send a single AMQP reply to call message. The current behaviour since oslo-incubator is to send two AMQP replies - first one with the payload, a second one to ensure the other have finish to send the payload. We are going to remove it in the N release, but we must keep backward compatible at the same time. This option provides such compatibility - it defaults to False in Liberty and can be turned on for early adopters with a new installations or for testing. Please note, that this option will be removed in the Mitaka release.