New in version 2.8.
| Parameter | Choices/Defaults | Comments |
|---|---|---|
| max_connections - | Default: -1 | Max number of concurrent client connections. Negative value means "no limit". Ignored when the state is absent. |
| max_queues - | Default: -1 | Max number of queues. Negative value means "no limit". Ignored when the state is absent. |
| node - | Name of the RabbitMQ Erlang node to manage. | |
| state - |
| Specify whether the limits are to be set or cleared. If set to absent, the limits of both max_connections and max-queues will be cleared. |
| vhost - | Default: "/" | Name of the virtual host to manage. |
# Limit both of the max number of connections and queues on the vhost '/'.
- rabbitmq_vhost_limits:
vhost: /
max_connections: 64
max_queues: 256
state: present
# Limit the max number of connections on the vhost '/'.
# This task implicitly clears the max number of queues limit using default value: -1.
- rabbitmq_vhost_limits:
vhost: /
max_connections: 64
state: present
# Clear the limits on the vhost '/'.
- rabbitmq_vhost_limits:
vhost: /
state: absent
Hint
If you notice any issues in this documentation, you can edit this document to improve it.
© 2012–2018 Michael DeHaan
© 2018–2019 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/2.9/modules/rabbitmq_vhost_limits_module.html