question

Upvotes
Accepted
24 7 9 14

ETA resiliency/failover management

I use an ETA API in a C++ application. I have a bunch of IP's (ADS endpoints) available to me. Primarily, my application would consume data from only one IP at a time. However, I would like to failover to an alternate IP (this could be a series of IP in a particular order) if there is a disconnect from my primary IP. My goal is to recover from the failure with primary IP as soon as possible and move over all my subscription to the second in line IP and so on. Is there a documentation that outlines do's, don'ts and best approach in handling the resiliency and failover ?

elektronrefinitiv-realtimeelektron-sdkrrteta-apielektron-transport-api
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
Upvotes
Accepted
4.4k 10 6 9

Hi @RAJ

First, please note that ETA Value Add has connection failover feature. If you use ETA RsslReactor, you can add more than one connection to RsslReactorConnectOptions.reactorConnectionList and the RsslReactor will attempt to reconnect to each host in the list.

If you opt for non-Value Add lib, then the application has to manage the failover by itself. There is no special document that outlines the do's and don'ts. But remember that the application must send login, directory, and item request again once it connected to a new ADS.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.