🎄 Happy Holidays! 🥳

Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.

Happy Holidays!

Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.

How to implement a failover mechanism by connecting the Solace HA through a single URL

bxb
bxb Member Posts: 12 ✭✭
in PubSub+ Event Broker #1

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.

This is the best practice ? 😲

Tagged:

Answers

  • bxb
    bxb Member Posts: 12 ✭✭
    #2

    @marc needs some suggestions, thanks a lot .

  • uherbst
    uherbst Member, Employee Posts: 130 Solace Employee
    #3

    Hi @bxb,

    Often used is a loadbalancer. I've seen running Solace HA groups behind F5s, nginx, haproxy (and maybe every other LB you can think of).

    Keep in mind: You need to load balance all ports for all protocols that you want to use.

    Uli

  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 644 admin
    #4

    Please use the healthcheck ports on the brokers for your load balancers! https://docs.solace.com/Admin/Load-Balancer-Health-Check.htm

    That what our own Solace Cloud uses for knowing which broker currently has activity.

  • bxb
    bxb Member Posts: 12 ✭✭
    #5
    https://solace.community/discussion/comment/7224#Comment_7224

    Hi @Aaron ,

    Thank you for your reminder~！

    I used NLB for load balancing my Primary and Standby nodes, and I used SMF port 55555 for health check, but found that it was not successful.

    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?

    image.png

  • bxb
    bxb Member Posts: 12 ✭✭
    #6
    https://solace.community/discussion/comment/7216#Comment_7216

    Yes, thank you very much~

    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

  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 644 admin
    #7

    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.

  • bxb
    bxb Member Posts: 12 ✭✭
    edited August 30 #8
    https://solace.community/discussion/comment/7241#Comment_7241

    Can I apply for support if I am using the Software Event Broker instead of the Cloud version ? 😁

  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 644 admin
    #9

    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.

Categories

This Month's Leaders

This Week's Leaders