SPK Fixes and Known Issues

This list highlights fixes and known issues for this SPK release.

SPK Release Notes SPK Release Information
Version: 1.7.14
Build: 1.7.14

Note: This content is current as of the software release date
Updates to bug information occur periodically. For the most up-to-date bug data, see Bug Tracker.


Cumulative fixes from SPK v1.7.14 that are included in this release
Known Issues in SPK v1.7.14

SPK Fixes

ID Number Severity Links to More Info Description
1813165-1 2-Critical TMM does not successfully connect to the Redis database.
1818381-1 2-Critical System may crash during Sentinel pod restart.

Cumulative fix details for SPK v1.7.14 that are included in this release

1813165-1 : TMM does not successfully connect to the Redis database.

Component: SPK

Symptoms:
TMM attempts to connect to the Redis database fail.

Conditions:
TMM attempts to establish a connection with the Redis DBs after DB/Sentinel pods experience downtime.

Impact:
TMM fails to establish a connection with the Redis DBs, resulting in downtime for the associated applications.

Workaround:
Restarting the TMM pod can help mitigate the issue.

Fix:
TMM successfully establishes a connection with the Redis DBs following DB/Sentinel pod downtime.

Summary of Code Level Change:
Connection cleanup function is enhanced to reset the request unsent counter which would allow connection retry when new request arrives.

1818381-1 : System may crash during Sentinel pod restart

Component: SPK

Symptoms:
TMM may crash while restarting and attempting to connect to the DSSM DB.

Conditions:
Attempting to reestablish the connection between TMM and the DSSM DB pod.

Impact:
TMM crashes and restarts.

Workaround:
None.

Fix:
The TMM successfully reestablishes the connection to the DSSM DB pod without restarting.

Summary of Code Level Change:
Code changes to introduce appropriate condition gates to validate the Sentinel connection state prior to the closure.


Known Issues in SPK v1.7.14


SPK Issues

There is no known issue in this release.


★ This issue may cause the configuration to fail to load or may significantly impact system performance after upgrade


*********************** NOTICE ***********************

For additional support resources and technical documentation, see:
******************************************************
ID Number Severity Links to More Info Description