Configuring Distributor and Workers

Component: Distributor
NuGet Package NServiceBus (3.x)
Standard support for version 3.x of NServiceBus has expired. For more information see our Support Policy.

Distributor configuration

The distributor requires an additional queue where workers can send their status updates. This is the control queue. The default address is endpoint_name.distributor.control.


The distributor stores metadata about the worker availability in the the queue with the suffix

It is valid for messages to be in the queue when the system is idle. The number of the messages should be the sum of the capacity of all workers. If each worker had a maximum concurrency level of 8 and there are 4 workers then there will be 32 message in the queue.

When hosting endpoints in NServiceBus.Host.exe

When running with NServiceBus.Host.exe, the following profiles start the endpoint with the distributor functionality:

To start the endpoint as a Distributor, run the host from the command line as follows:

NServiceBus.Host.exe NServiceBus.Distributor

The NServiceBus.Distributor profile instructs the NServiceBus framework to start a distributor on this endpoint, waiting for workers to enlist to it. Unlike the NServiceBus.Master profile, the NServiceBus.Distributor profile does not execute a worker process.

It is also possible to use the NServiceBus.Master profile to start distributor and worker processes on the endpoint. To start the endpoint as a master, run the host from the command line as follows:

NServiceBus.Host.exe NServiceBus.Master

When self-hosting

When self hosting the endpoint, use this configuration:

// Running the Distributor and a Worker
// or

// Running the Distributor only
configure.RunDistributor(withWorker: false);

Worker configuration

Any NServiceBus endpoint can run as a worker node. To activate it, create a handler for the relevant messages and ensure that the app.config file contains routing information for the distributor.

When hosting in NServiceBus.Host.exe

If hosting the endpoint with NServiceBus.Host.exe, to run as a worker, use this command line:

NServiceBus.Host.exe NServiceBus.Worker

Configure the name of the master node server as shown in this app.config example. Note the MasterNodeConfig section:

    <!-- Other sections go here -->
    <section name="MasterNodeConfig"
             type="NServiceBus.Config.MasterNodeConfig, NServiceBus.Core" />
  <!-- Other config options go here -->
  <MasterNodeConfig Node="MachineWhereDistributorRuns"/>

For more information, see DistributorControlAddress and DistributorDataAddress in the Override distributor queues (advanced) section.

When self-hosting

When self-hosting the endpoint, the following code will enlist the endpoint with a distributor.


Similar to self-hosting, when running NServiceBus prior to version 6, ensure the app.config of the worker contains the MasterNodeConfig section to point to the hostname where the distributor process is running.


The distributor can be used in combination with the outbox feature. Outbox must be enabled on the workers. It must also be enabled if a worker is configured as distributor master (distributor/worker combination). Outbox is required only for persistence operations; the forwarding of messages to workers is purely a transport operation and outbox will not participate in the forwarding logic.


Override distributor queues

The distributor process uses two queues for its runtime operation. The DataInputQueue is the queue where the client processes send their messages. The ControlInputQueue is the queue where the worker nodes send their control messages.

The NServiceBus default values for these settings can be overridden, as shown in the UnicastBusConfig section below:

<UnicastBusConfig DistributorControlAddress="EndpointName.Distributor.Control@MachineWhereDistributorRuns"
    <!-- regular entries -->

Prioritizing on message type

Similar to standard NServiceBus routing, it is not desirable to have high priority messages to get stuck behind lower priority messages, so just as it is possible to have separate NServiceBus processes for different message types, it is also possible to set up different distributor process instances (with separate queues) for various message types.

In this case, name the queues after the message type. For example: SubmitPurchaseOrder.StrategicCustomers.Sales becomes the name of the distributor data queue and the input queues of each of the workers.

Last modified