Hello team,
We have Upgraded Pega Platform from 8.6.6 to 23.1.4 and when we scan the system, this Critical Missing Hotfix appears:
HFIX-C1343 Port the functional change to migrate HZ use case to alternative
but we haven’t received any CAD advise or INC.
Please, could you help us to identify if this HF applies to us?
How to test it after install the HF?
Regards.
@Iñaki Ruiz You could try the Pega 23.1.5 Patch Release Pega Infinity '23.1.5 - Patch Release Available! | Support Center
@Iñaki Ruiz
that hotfix is about migrating any remaining Hazelcast (HZ) use to Pega’s newer clustering approach in 23.1.4. First, confirm it applies by checking your Upgrade Scan/Guardrails report for Hazelcast references or “cluster” warnings and by searching the hotfix ID in My Pega Support; if it’s flagged as Critical Missing, assume you need it. Request HFIX-C1343 from Pega Support and install it in a lower environment using Hotfix Manager, then restart all nodes. After install, validate cluster health: nodes join cleanly, no Hazelcast jars load, and Pulse, queue processors, job schedulers, and real-time containers run without errors. Do a quick failover check by stopping one node and confirming assignments, locks, and sessions behave normally. Regression test case creation, work routing, and background processing; watch PDC for new alerts/errors. If everything is clean, promote to higher environments with a rollback plan and document DSS/rule changes noted in the hotfix readme.
Hello, we continue using embedded Hazelcast, so we guest that this HF doesn’t apply to our configuration
we have this parameter in all of our nodes:
wlpega@es1048yr(prpc):/opt/weblogic/wlpega/PEGA/bin>grep -i hazelcast setUserOverrides.sh
-DNodeSettings=services/stream/provider=Internal;dsm/services/stream/pyBaseLogPath=/opt/SP/pegaapp/pega/kafka;cluster/hazelcast/v5/enabled=true \
Regards
Hello, please could you give us the impact of applying this Hotfix HFIX-C1343? , since we are still using embedded Hazelcast and we understand that the hotfix indicates that the internal Hazelcast components will be removed, right?
With the Upgrade we did from version 8.6.6 to version 23.1.4, we have not installed any external Hazelcast (Clustering Service). We only added this entry in the setUserOverrides.sh:
-DNodeSettings=services/stream/provider=Internal;dsm/services/stream/pyBaseLogPath=/opt/SP/pegaapp/pega/kafka;cluster/hazelcast/v5/enabled=true \
so we understand that we are still using the internal Hazelcast and this HF doesn’t apply to our configuration.
Regards.
@Iñaki Ruiz HFIX-C1343 is meant for apps that still call old Hazelcast behaviors that Pega removed/changed in 23.1, not for environments simply running embedded Hazelcast v5. Since your nodes show cluster/hazelcast/v5/enabled=true and services/stream/provider=Internal, you’re on the supported embedded HZ v5 path, so the hotfix likely adds no value and won’t “remove” your embedded cluster. To be sure, search your rules and logs for deprecated HZ APIs (e.g., legacy v3 maps/caches) or upgrade scan warnings tied to Hazelcast; if none, you can skip it. If you do install it, impact is functional only (no external HZ is introduced, no config flip), and it just reroutes any lingering legacy calls to the alternative used in 23.1. Test by restarting the cluster, confirming all nodes join, queue processors and job schedulers run, and no Hazelcast deprecation errors appear. Verify Pulse, assignments, locks, and case routing across a node bounce. Check PDC for new PEGAxxxx alerts related to cluster/cache after the change. Remember stream=Internal (Kafka) is separate from clustering; this hotfix doesn’t alter that. Document your finding (“no deprecated HZ usage detected; HFIX-C1343 not applicable”) or, if applied, note “no config changes required; regression passed.”