Reasons for change
- XML-RPC code changes:
- Optimization of the network bandwidth usage in overlay mode
- More friendly for the XML-RPC servers: split long requests into smaller ones
- More fault-tolerant and efficient: send the XML-RPC requests to a pool of servers in parallel, instead of to a single server
Test Procedure
This version has been tested on the DEV server.
Rollback procedure
Version 2.0.3 could be reinstalled
CCB Jira
Details
- Code separation between Oracle and XML-RPC data retrieval methods
- XML-RPC code changes:
- Optimization of the network bandwidth usage in overlay mode: the mnemonics are grouped into the requests (IOT-101@JIRA)
- More memory-friendly for the XML-RPC servers: the timespan of the individual requests cannot exceed 24 hours. Larger requests are permitted, but split into smaller ones (IOT-102@JIRA). There is no limit on the length of the timespan on the client side
- Distributed requests: instead of using 1 single XML-RPC server, we send to a pool of servers (IOT-103@JIRA). This is more friendly for the servers, and more efficient because the requests can be sent in parallel (IOT-104@JIRA), with a controlled degree of concurrency defined per server (for now: if more than 1 request for a given server is in flight, the others are queued. This can be increased later)