Proper behavior for an interactive provider upon loss of upstream communication
Hello All,
Can someone tell me what the proper behavior is for an interactive provider connected to TREP that looses its upstream communication. We are sending Closes for all its items if singleOpen is True and Close-Recover if singleOpen is set to False. The problem is that if singleOpen is True, the items are never recovered, and if False, the items are put on the recovery queue and not recovered for two minutes. The preferred behavior is to have the items recovered immediately. Is this the correct behavior or should they be doing something different? Where can I find documentation about the correct behavior in this situation.
Thanks
Best Answer
-
SingleOpen = true means the provider drives the recovery, which means the provider detects upstream status and provides feedback to the consumer. The provider should update the service directory to set ServiceState to "down", and optionally AcceptingRequests to "down".
If there are multiple providers as hinted then the provider can publish a "source directory link filter entry" to indicate the upstream status.
When SingleOpen = false the consumer is driving the recovery so it is completely beholden to the consumers implementation.
Generally one should be using the directory state filter if the entire service is down so that TREP may redirect all requests to an active provider.
0
Answers
-
Thanks Steve. Do you know if there is some documented "Best Practice" or guideline on how to handle this situation. I looked in the RDM Usage guide but I couldn't find anything specific.
0 -
In absence of documentation each configuration needs to be explicitly tested for and validated that it is a supported operation. Unfortunately there is often a large number of permutations and variance between versions on some features.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 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
- 367 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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛