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:
| Item | Currently | Changing 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 should need to set the AMQP heartbeat on your client settings to 60 seconds to match so that it matches the server's expectations. Otherwise, the server may think that you are no longer connected. The short 60s This smaller heartbeat value will generate network traffic every 60s, thus preventing network devices from dropping your connection because when it 's been idle for too longis idle. |
| Publish confirms | Recommended | Strongly recommended | If you publish messages, you're ve always been expected to use publish confirms or risk not being notified of failed messages. With a clustered environment, this This is even more important in a clustered environment. |
Timeline
| Date | Event |
|---|---|
| Jul 24 2019 | Test cluster environment is available for developers to test |
| Oct 20 2019 | Production migration to cluster environment |
...