MC2 Release Notes - November 15 2022

Component versions

Version to request for All Services install: 2022.11.15.2

EAGLEINSTALLER 2022.11.15.1
EAGLEML 2022.11.15.1
EAGLEML-W-O 2022.11.15.1
EXTRACTSERVICERULES 2022.11.15.1
IMPORTSERVICERULES 2022.11.15.1
MC2 2022.11.2
kafkaservice 2022.11.1
pypy 2022.10.2
pyruleservice 2022.11.9

openjre:
openjdk version "11.0.16" 2022-07-19
OpenJDK Runtime Environment 18.9 (build 11.0.16+8)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.16+8, mixed mode)

pace report service (installed separately):
pace-reportservice-1.0.10.jar

 

Some additional steps are needed to install on top of October 2022 or original version of November 2022:

Stop MC2

Kill pypy on backend with

  • /bin/kill -9 pypy

Install the updated All Services release


SDP-68125 pypy processes continue running when extractservice (mc2) is stopped

Updated pypy startup

Updated pypy startup so that pypy processes will exit when extractservice is shutdown.

 

SDP-67535 Develop - Expose machine 'hostname' to MC HealthCheck JSON and Email alert templates

Exposed Machine Host Name to MC HealthCheck

A request was made to expose Host Name in the MC HealthCheck Email and Json alert templates. The code was updated to support this feature.

 

SDP-66765 Update eagle_default/in/xml/xml-ref_schedule.xml for correct processing in MC2 Engine

Updated EagleML ref schedule load logic

Updated EagleML ref schedule load logic to function correctly when executed in the MC2 engine.

File changed: eagle_default/in/xml/xml-ref_schedule.xml

 

SDP-66482 [Profiled generic load] Pass custom parameters to load steps

Updated workflow generator to enable passing custom parameters to profiled load

Updated workflow generator to enable passing custom parameters to profiled generic load

 

SDP-65993 MC2 2022_11_15 Release - Health Check may not send alerts for one monitoring type

HealthCheck Alerts were not Sent

HealthCheck Alerts were not sent due to incorrect identification of master status.

The code was updated to fix the issue.

 

SDP-50813 Enable ability to define a timeout for EDS extract execution

Enabled configurable global timeout for EDS processing

Enabled a configurable global timeout for EDS processing.
To define a timeout value (for example for 90 minutes),
add the below (or create the file if it does not exist already) to
estar/tpe/dynamic/pyrules/custom/env.py:

 

def get_default_timeout_minutes():
return 90

and cycle MC2 on all application servers.

An extract reaching the timeout interval will include the following in status reply message:

"status":"FAILED","severityCode":

{"value":"1"} ,
"reason":[

{"description":"Request processing timed out after *** seconds"}

Â