When we configuring a Solace HA (Software) cluster, Solace clients can usually connect to the primary and backup nodes of Solace HA to achieve automatic switching of primary and backup node failures.
But, for Solace clients, configuring and managing two connection addresses can be a bit troublesome.
To simplify client configuration, I think a virtual IP or load balancer address can be used instead of a specific physical node address:
1、Use a load balancer or Nginx reverse proxy to connect Solace’s primary and backup nodes.
2、Use Keepalived to create a virtual IP for Solace’s primary and backup nodes to achieve high availability.
Although there still seem to be some issues at the moment, I have tried using NLB to load balance my primary and standby nodes.
As Aaron reminded, it is also necessary to configure health checks for NLB, so that NLB can switch between primary and backup nodes instead of just splitting them
According to the Solace documentation, do I just need to open my 5550 port and configure my NLB to perform health checks through this port?
I think so? If you do some testing and it’s not behaving as expected, I could ask one of our Cloud Ops people to explain how they do it in Solace Cloud.
If by “apply for support” you mean contact/use Solace’s Support personnel, you can purchase various support plans. They’re documented here: https://solace.com/support/ I’m not sure of the costs though. But you can even get support on the Standard edition (e.g. free) broker… we have quite a few customers running the free Standard broker in production (vs. Enterprise $$) and only paying us for Support.