SR-D68707 · Issue 529869
Update Handler will not run during migration
Resolved in Pega Version 8.3.2
Rolling restart of DataFlow, ADM ,VBD, and Util Tiers failed with a PENDING_JOINING error after an in-place upgrade. This was traced to the logic for the update timing: when nodes start after an upgrade from 7.x to 8.x they will migrate data flow runs. Migration happens on only one node, and while it's in progress the other nodes will wait until migration finishes before they come up. At this point the state of the data flow services will be 'PENDING JOINING'. The issue is that while migrating runs, the Data Flow Update Handler was triggered to validate whether there were nodes available on the service the run belongs to. This call can cause the corresponding data flow service to be initialized, but the call will be blocked since all services wait for the migration to end. This resulted in a deadlock which prevented all nodes from coming up successfully. To resolve this, the process has been updated to skip the update handler during migration to avoid triggering the initialization of client services that are waiting on the migration lock.
SR-D69028 · Issue 528972
Deadlock in static Initialization of IntList resolved
Resolved in Pega Version 8.3.2
JVM Deadlock was seen related to the static Initialization of a subclass field in class com.pega.decision.strategy.ssa.runtime.collections.api.IntList . Thread dumps showed threads in RUNNABLE State that were parked to wait for class initialization, and this was traced to a missed sonar alert which failed in multi-threading. To resolve this, the system handling has been updated to prevent potential deadlock.
SR-D71621 · Issue 533294
Real time processing picks up correct datetime for Capture Response records
Resolved in Pega Version 8.3.2
A Realtime Data flow for the Capture Response flow was configured with a strategy shape set to load previous decisions within the past 7 days. Once this Realtime DF was started, attempting to Capture Response for decisions made after that startup timepoint did not work. This was traced to the InteractionID being written with global properties for the datetimes, and has been resolved by making those datetime properties local so the start and end time are not cached and the time range is calculated based on "now”.
SR-D74117 · Issue 539460
DDS service will not run Hazelcast check if external Cassandra is configured
Resolved in Pega Version 8.3.2
Services were not responding, and thread dumps seen in the logs indicated that a large number of threads were waiting for one to come back from getting the cluster state for a DSM process. Investigation showed that the threads were waiting for a Hazelcast response about the cluster state. However, since a Hazelcast call is not needed when Pega is configured with external Cassandra, the DDS Service code has been changed to not to check for candidate nodes if configured with external Cassandra cluster.
SR-D74247 · Issue 542915
Resolved errors when using Build Model from the Preview Console
Resolved in Pega Version 8.3.2
Using the Web Chatbot interface and trying to perform Build Model action from Preview Console failed with multiple errors, either "This action is not allowed as it is outside the current transaction" or "class <blank> doesn't exist". This was traced to issues with the transaction during model update, and has been resolved by conditionally disabling the show page step of pzGetModelProcessStatus. This step creates a difference in the context of the current transaction and is disabled when called from Update API.
SR-D75519 · Issue 536717
Corrected calculating propensities
Resolved in Pega Version 8.3.2
Several PMML models designed to compare the outcomes to a control dataset experienced an issue where the probability scores in Pega did not match the original control dataset. The PMML model was also tested using KNIME; those results matched Pega but not the original control dataset. Investigation showed that the JPMML evaluator contained outdated code, and the incorrect calculations have been resolved.
SR-D78940 · Issue 542925
Dataflow monitoring enhanced
Resolved in Pega Version 8.3.2
Enhanced monitoring and healthchecks have been added for dataflow and alerts.
SR-D79145 · Issue 543053
Added tokenizer for KeyWord-Based Topic Detection phrases
Resolved in Pega Version 8.3.2
KeyWord-Based Topic Detection was not Working for "Enrollment/Re-Enrollment" as a word, for example a categorization model with the text 'This is an email related to Enrollment/Re-Enrollment'. To facilitate this use, a tokenizer has been added to break should, must, and and words into components for a taxonomy match.
SR-D79909 · Issue 542243
DDS added for automated dataflow run cleanup
Resolved in Pega Version 8.3.2
During a recent upgrade it was seen that there were in excess of 20k dataflow runs, some 2 years old, which slowed down the migration significantly. In order to resolve this, an automated process has been added. This clean-up procedure deletes all the single case, batch, and real time runs older than 30 days which are in the final state - Completed, Completed with Failures, or Failed, and batch and real time runs which are in the Stopped state. The DDS Pega-DecisionEngine.dataflow/run/maxDaysToKeepRuns.should be used configure the retention period. Note that the retention period is calculated since the last processed message and not the creation time of the run.
SR-D82895 · Issue 543605
Restart issue on dataflow service nodes resolved
Resolved in Pega Version 8.3.2
A high percentage of rolling restarts were failing for nodes hosting dataflow services due to prolonged restart times. To resolve this, the system has been updated so Cloud services will not try to recover the node state in case of a restart, since nodeIDs are always new and not reused.