---
schema_version: "1"
id: c40bccde91ec23b6271ec04c2020195a64401c91c90900651ba1fda27c6d7d28
title: Deploy MQTT Connector Apps in a Cluster
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mqtt3-connector/1.0/mqtt3-connector-cluster.md
canonical_url: https://docs.mulesoft.com/mqtt3-connector/1.0/mqtt3-connector-cluster
source_site: docs.mulesoft.com
content_type: documentation
content_hash: c62bf70580b5259d915789a03e0af49b283cda5839154256a05d2b246f55f7f3
description: MuleSoft Documentation Site
release: "1.0"
latest: false
---
---
product: MQTT Connector
version: 1.0
---

# Deploy MQTT Connector Apps in a Cluster

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

MQTT broker establishes a connection with a client using its client ID. For example, if the broker
establishes a connection with a client whose client ID is `smart-bentley-123`, and then the broker
receives a new connection with the same client ID, the broker closes the previous connection
(assuming it is stale) and accepts the new connection. This mechanism is known as a client takeover.
MQTT brokers employ this mechanism to prevent situations such as TCP connections reaching a
half-open or invalid state due to a crash in one of the communication ends, which is undesirable.

Because of client takeover, Mule runtime engine (Mule) applications that use MQTT Connector deployed
in a cluster must include a unique client ID for each active node in the cluster. To avoid client
takeovers in this kind of scenario, you can supply these unique IDs either by using the
application-provided client ID generators or by providing your own client ID generator.

## See Also

- [Set a Client ID with MQTT Connector](https://docs.mulesoft.com/mqtt3-connector/1.0/mqtt3-connector-client-id)

- [MQTT Connector Examples](https://docs.mulesoft.com/mqtt3-connector/1.0/mqtt3-connector-examples)

- [Salesforce Help](https://help.salesforce.com)