You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I'm using your library (thank you) to connect to Amazon MQ (ActiveMQ) which has a failover protocol with multiple endpoints. It currently runs in Standby mode which means there is one instance running at a time, and when needed a standby instance pops up. It happens when AWS upgrades MQ versions for example.
Do you think it would be interesting to handle this failover mechanism?
What's usually implemented is to pass multiple urls in options, try one, and if it's down, try another one. rhea doesn't seem to handle failover protocol.
The text was updated successfully, but these errors were encountered:
Failover is not supported at the moment, mostly because rhea itself does not support it.
We had the exact same setup in one of our projects, with that our solution was to have both the Active and Standby brokers be present in the same target group, have a load balancer pointed to said target group, and have a nice CNAME pointing to the LB, and this CNAME is what we use in the application it self.
Hello,
I'm using your library (thank you) to connect to Amazon MQ (ActiveMQ) which has a failover protocol with multiple endpoints. It currently runs in Standby mode which means there is one instance running at a time, and when needed a standby instance pops up. It happens when AWS upgrades MQ versions for example.
Do you think it would be interesting to handle this failover mechanism?
What's usually implemented is to pass multiple urls in options, try one, and if it's down, try another one. rhea doesn't seem to handle
failover
protocol.The text was updated successfully, but these errors were encountered: