This was migrated to https://github.com/rabbitmq/rabbitmq-server
This repository has been moved to the main unified RabbitMQ "monorepo", including all open issues. You can find the source under /deps/rabbitmq_peer_discovery_consul. All issues have been transferred.
This is a Consul-based implementation of RabbitMQ peer discovery interface (new in 3.7.0, previously available in the rabbitmq-autocluster plugin by Gavin Roy).
This plugin only performs peer discovery and most basic node health monitoring using Consul as a data source. Please get familiar with RabbitMQ clustering fundamentals before attempting to use it.
While it may seem at times that this is a RabbitMQ cluster management solution, it is not. Cluster provisioning and most of Day 2 operations such as proper monitoring are not in scope for this plugin.
This plugin requires RabbitMQ 3.7.0 or later.
For a Consul-based peer discovery and cluster formation mechanism that supports 3.6.x, see rabbitmq-autocluster.
This plugin ships with supported RabbitMQ versions. There is no need to install it separately.
As with any plugin, it must be enabled before it can be used. For peer discovery plugins it means they must be enabled or preconfigured before first node boot:
rabbitmq-plugins --offline enable rabbitmq_peer_discovery_consul
See RabbitMQ Cluster Formation guide.
See CONTRIBUTING.md and our development process overview.
Licensed under the MPL, same as RabbitMQ server.
(c) 2007-2020 VMware, Inc. or its affiliates.