Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 3 Next »

Overview

We plan to upgrade the UH Message Broker from a single host to a clustered environment to improve availability. Here is what you can expect:

ItemCurrentlyChanging to…Comments
Server configuration

Single server

3-node cluster
Software versions

RabbitMQ 3.1.5

Erlang 19

RabbitMQ  3.7.12 or higher

Erlang 21.2.6 or higher


RabbitMQ client

Existing clients appear to work.  Will confirm whether any upgrades are necessary.
AMQP heartbeat

Default is 65535 seconds (18.2 hours)


Default is 60 seconds

You need to set the AMQP heartbeat on your client settings to 60 seconds so that it matches the server's expectations. Otherwise, the server may think that you are no longer connected.

This smaller heartbeat value will generate network traffic every 60s, thus preventing network devices from dropping your connection when it is idle.

Publish confirmsRecommendedStrongly recommendedIf you publish messages, you've always been expected to use publish confirms or risk not being notified of failed messages.   This is even more important in a clustered environment.

Timeline

DateEvent
Jul 24 2019Test cluster environment is available for developers to test
Oct 20 2019Production migration to cluster environment
  • No labels