Fault Tolerance in Elektron Price Feed (RTO) in WarmStandbyMode

Hi,
I use WarmStandbyMode in my process to receive Elektron Price Feed. Whenever there's a freeze in connection between my application and active server, how long does it take to switch from active server to standby server? Is there a parameter through which it can be tuned ? In a situation where both active and standby server connections are frozen, what would be the behaviour ? For some reason, if primary server is down (when that happens, standby server connection becomes active), is adding another standby connection an option while application is still running ?
Best Answer
-
Thanks for reaching out to us.
I am not sure what you mean by connection freeze. Typically, the warm standby feature allows a consumer to failover to a standby connection when a primary connection is down, or a service is down.
However, if the channel is still connected but is unable to send or receive anything, the API uses a ping mechanism to detect this kind of problem. The ping mechanism can be configured via the following configuration in the channel.
The ping timeout setting on the server side may override this client's setting.
We don't have an exact number of how long it takes to switch from active server to standby server but it will be faster than the normal reconnection because the standby server is already aware of items an application has subscribed for, during a failover the API doesn't need to re-subscribe items to the standby server.
I did a quick test by enabling tracing in the API and checking the time when the channel was down and the time when the item was recovered. I found that with the normal reconnection logic, it took around 3 seconds to recover an item but with the warm standby feature, it took only 300 milliseconds to recover an item. These are not official numbers and they may be different in your environment.
If both active and standby servers are down, the API can't connect to the servers and is unable to get the data. You can't add more standby servers in the consumer after the consumer was created. In this case, you need to create a new consumer with new configurations.
For more information, please refer to the Introduction to Refinitiv Real-Time SDK Warm Standby Feature article.
I hope that this information is of help.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛