If adh switch between active and standby could not send close events for the most subscribed reques
If adh switch between active and standby could not send close events for the most subscribed requests how to ensure it send?
The interactive provider needs to receive close events for all the symbols or request tokens when adh switches between active and standby, when there are a large number of such requests, adh only send a part of it, how to get the adh to send close events for the complete set of subscriptions. The interactive provider is an C++ application using RFA.
Best Answer
-
In the Hot Standby mode, each ADH (Active or Standby) connects to its own source application. They subscribe to the same item and retrieve the same update messages from the source applications. When using Hot Standby, each datafeed/source application must deliver the same update stream for each item open on the datafeed; i.e., the order of update delivery and the update’s data content must be the same for a given item.
Though both servers receive updates for an open item, only the active server transmits the updates to a sink (ADS). The standby server records all updates in synchronization buffers (which store all updates not sent by the active server). If there is a failover, the standby server plays these updates to the network.
When the connection between the active ADH and its source application is down or the source application connected by the active ADH is down, the standby ADH takes the role of an active server and then transmits the updates to an ADS.
I am not sure why ADH needs to send close requests to the source applications when ADH switches between active and standby. Please explain more about the use case.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 162 App Studio
- 4 Block Chain
- 5 Bot Platform
- 17 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 370 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛