Clustered RabbitMQ transport usage

NuGet Package: NServiceBus.RabbitMQ (7-pre)
This page targets a pre-release version. Pre-releases are subject to change and samples are not guaranteed to be fully functional.


Ensure a RabbitMQ cluster is running is running and accessible. The following docker commands will set one up if needed:

docker network create --driver bridge network1

docker run -d --network network1 --hostname rabbit1 --name rabbit1 -p 5672:5672 -p 15672:15672 -e RABBITMQ_ERLANG_COOKIE='asdfasdf' rabbitmq:3-management
docker run -d --network network1 --hostname rabbit2 --name rabbit2 -p 5673:5672 -p 15673:15672 -e RABBITMQ_ERLANG_COOKIE='asdfasdf' rabbitmq:3-management
docker run -d --network network1 --hostname rabbit3 --name rabbit3 -p 5674:5672 -p 15674:15672 -e RABBITMQ_ERLANG_COOKIE='asdfasdf' rabbitmq:3-management

docker exec rabbit2 rabbitmqctl stop_app
docker exec rabbit2 rabbitmqctl join_cluster rabbit@rabbit1
docker exec rabbit2 rabbitmqctl start_app

docker exec rabbit3 rabbitmqctl stop_app
docker exec rabbit3 rabbitmqctl join_cluster rabbit@rabbit1
docker exec rabbit3 rabbitmqctl start_app

Code walk-through

This sample shows how to use a clustered RabbitMQ as a transport for NServiceBus to connect two endpoints. The sender either sends a command or publishes an event to a receiver endpoint, via the RabbitMQ broker, and writes to the console when the message is received.


var transport = new RabbitMQClusterTransport(Topology.Conventional, "host=localhost", QueueMode.Quorum, DelayedDeliverySupport.Disabled);

The username and password can be configured via the connection string. If these are not present, the connection string defaults to host=localhost;username=guest;password=guest.

Note that delayed delivery isn't supported for clusters and the sample therefore disables them. This means that saga timeouts can't be used and delayed retries must be disabled as shown below:

// Delayed retries needs to be disabled since we can't safely use the timeout capabilities of the transport
endpointConfiguration.Recoverability().Delayed(dc => dc.NumberOfRetries(0));

Adding nodes

RabbitMQ allows additional nodes to be added to avoid having to use a load balancer in front of the cluster. Adding those nodes will make the connection manager use them in a round robin fashion and automatically re-connect to healthy nodes should the connection be lost.

RabbitMQ defaults to port 5672; the extra nodes (rabbit2 and rabbit3) are added as shown below:

// if you have setup the 3-node cluster as mentioned in the sample instructions
transport.AddClusterNode("localhost", 5673);
transport.AddClusterNode("localhost", 5674);

With this setup the connection manager will initially connect to rabbit1 but try rabbit2 or rabbit3 should rabbit1 become unavailable.

To test this, shutdown node rabbit2:

docker exec rabbit1 rabbitmqctl stop_app

Notice that a WARN message is logged and that the endpoint is reconnected to the cluster.

Related Articles

Last modified