We are working to complete the externalization of Hazelcast as part of our anticipated Pega 23.1.1 upgrade and are looking for some guidance from Pega to confirm we are completing this effort correctly.
We are looking to understand:
- How to verify hazelcast externalization and migration of data if needed?
- How to test if externalize hazelcast is working and pega is no longer using internal hazelcast?
- Is hazelcast data migration needed? if so, what is migrated and how does one validate that the migration has migrated everything that it should?
@NadeemM8116
To verify Hazelcast externalization, you can use the REST Endpoint rule pzcluster/hazelcast/info under the CloudRemoteAPI service package in Dev Studio. This will confirm the Hazelcast release running your Hazelcast deployment service.
To test if external Hazelcast is working and Pega is no longer using internal Hazelcast, you can check the communication between your Pega nodes and the Hazelcast cluster. If the service automatically configures the communication, it means that Pega is using the external Hazelcast.
Regarding data migration, when you migrate from embedded Hazelcast to the Clustering Service, you can use Pega-provided Docker images and Helm charts to configure a zero-downtime migration. However, the specifics of what is migrated will depend on your particular setup and requirements.
To validate that the migration has migrated everything that it should, you can review the Hazelcast release running your Hazelcast deployment service. If the correct version of Hazelcast is running, your Pega Platform deployment is running with the externalize service.
This is a GenAI-powered tool. All generated answers require validation against the provided references.
Confirm the Hazelcast release running in your deployment
Migrating from embedded to external Hazelcast on Kubernetes