Does horizontal scaling for RFA 8 provide failover as well ?

Best Answer
-
Hello @ankit3.srivastava
Horizontal Scaling is used to further distribute the processing of events between multiple CPU cores. Hence, the number of events can be processed in time by multiple threads and there are no a lot of events pending in the queue which can cause Out-of-Memory.
RFA attempts to connect to the server(s) in the serverList configuration of connection node. If your serverList contains only 1 hostname/IP address, when the host/server goes down RFA still attempts to connect to the down server. To make RFA attempt to connect to another server when the connected server goes down, you have to set the serverList to have multiple hostname/IP address. For example:
The figure above shows the serverList contains 3 hosts. Assume
that RFA connects to the first server(192.168.27.99) then the server goes down.
Next, RFA attempt to connect to the second server(192.168.27.11). If it fails,
it attempt to the third server(192.168.27.48).In summary, you can use Horizontal Scaling with failover by
configuring multiple hosts in the serverList parameters.0
Answers
-
@ankit3.srivastava Are you referring to horizontal scaling as described in RFA dev guide?
In that case, scaling is in reference to running multiple threads - typically one per core, and does not provide any builtin failover. Your app will have to identify failure and implement re-subscription to the active connection.
0 -
The elements of the answer to your question have been given
by Pimchaya, but I think there is confusion here, so let me try to clarify. The
confusion is between the horizontal scaling of the real time platform (TREP)
and the horizontal scaling of the RFA application.In the first case, the platform can be scaled up to match a
growing number of client applications. To do so, the platform admin adds more
hosts (ADS - Advanced Distribution Server) to the platform. Having a redundancy
of ADS also enables failover if one of the ADS goes down.In the second case, the application can be scaled up to
match a growing number of incoming events. To do so, the application can run
several threads that will dispatch RFA events in parallel. This is what Pimchaya
explained in the first part of her answer.Your question is about the RFA failover mechanism. As you
understood, this is related to the platform horizontal scaling (or redundancy)
but has nothing to do with the RFA horizontal scaling, hence the confusion. The
answer to your question is given by Pimchaya in the second part of her answer.
If your TREP has several hosts (ADS) then set their IPs in the serverList RFA
parameter. This will enable the RFA failover mechanism.0 -
As Olivier mentioned in the answer below, Horizontal Scaling and Failover have different purposes.
- Horizontal Scaling is used to utilize CPU's cores, which increase event handling throughput via multi processing threads.
- Failover is used to switch to the next server in the serverList when the current connecting server goes down.
0 -
Back to your question, when using both HS and Failover together, what if one of the servers goes down.
Referring to Pimchaya's example, RFA will connect to the first server in the list (192.168.27.99). If the others are down, it doesn't affect to the current connection established. On the other hand, it will switch to the next valid server in the list.
Here there are possibilities:
- When all HS thread chains use the same serverList sequence, all HS thread chains will experience the same result.
- Otherwise, each HS thread chains will encounter different result depending on serviceList sequence.
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
- 688 Datastream
- 1.4K DSS
- 620 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
- 254 ETA
- 557 WebSocket API
- 38 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
- 276 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
- 663 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 229 TRKD
- 917 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 中文论坛