Reasons for change
- XML-RPC code changes:
- Using the much simpler "version 1" of the xml-rpc getTrending protocol
- Allow up to 4 simultaneous requests per server because the xml-rpc server is now fully multi-process
- Limit the timespan of a web trending request to 7 days (instead of 24hr)
Test Procedure
This version has been tested on the DEV server: http://glast-tomcat03:8080/TelemetryTrending
Rollback procedure
Version 2.1.0 could be reinstalled
CCB Jira
Details
- updated the code in DataChannel.java to un-marshall the trending data according to the "version 1" of the getTrending xml-rpc protocol, as described in DATA_FORMATS.txt
- changed the MAX_CONTENTION constant to 4, to allow 4 simultaneouos rpc to the same server. This is because the servers are now multi-process, 1 process per CPU core. The machines being quad-core, we have 4 server processes on each
- changed the SPLIT_REQSPAN_MS constant to -1, to disable splitting large requests into smaller sub-requests sent to different servers. This is because this is done locally on each server, to take advantage of the multi-core, and we want to maximize cache usage on each server (don't distribute the data too much)
- changed the MAX_AUTO_REQSPAN_MS constant to 7 days, to allow users to request trending graphs over a larger period.