This HiveMQ extension allows your HiveMQ cluster nodes to discover each other dynamically by regularly exchanging their information via etcd.
HiveMQ instances are added at runtime as soon as they become available by placing their information, on how to connect to them, to the configured key. The extension will regularly check the configured etcd key for files from other HiveMQ nodes. Additionally every broker updates its own entry on a regular basis to prevent the entry from expiring.
extensionsfolder of your HiveMQ nodes.
etcdDiscovery.propertiesfile for your needs or set environment variables
The information each node writes into etcd consists of an ip-address and a port.
The ip-address and port are taken from the
external-port which is configured in the cluster
transport (config.xml). If they are not set, the
bind-port will be used.
etcdDiscovery.properties can be reloaded during runtime.
etcdDiscovery.properties will always take precedent over environment variables.
|key||HIVEMQ_ETCD_KEY||Key to store discovery entries at|
|etcd-endpoint||HIVEMQ_ETCD_ENDPOINT||x||The region in which this S3 bucket resides.|
|etcd-port||HIVEMQ_ETCD_PORT||etcd port to connect at|
|expiration||HIVEMQ_ETCD_EXPIRATION||Time in seconds after which an entry in etcd is considered expired|
|update-interval||HIVEMQ_ETCD_UPDATE_INTERVAL||Time in seconds after which an entry in etcd is refreshed (Must be smaller than
|use-tls||HIVEMQ_ETCD_USE_TLS||Use TLS for connection to etcd|
|ca-path||HIVEMQ_ETCD_CA_PATH||Certificate authority to use for validating tls connection to etcd - if not set, system certificates will be used|