we are using the below configuration to form hazelcast cluster for our application and currently use only one datacenter (primary datacenter) forming cluster with this datacenter.
But i wanted to form the hazelcast cluster across cluster like primary datacenter & secondary datacenter each datacenter having 5 docker containers (totally 10 containers). Instead of using the IPaddress:port, is there anyother option to connect?
Pega configuration *******
***********
In spring boot application we use like below, which helps to connect hazelcast across datacenter
Use external Hazelcast for both data centers and configure the Pega cluster to join it by DNS hostnames or service names, not by changing to a Spring Boot style portName setting. Pega Infinity 23 documentation says Hazelcast connection details are configured through Pega settings such as DSS or prconfig.xml, and for container deployments Pega provides its own external Hazelcast image and Helm-based setup. What this really means is that Pega does not use the Spring Boot service-key.portName discovery pattern here. So the single fix is to create stable, resolvable names for the Hazelcast members or service endpoints in both data centers and use those names in the Pega Hazelcast member configuration. This keeps the 10 containers in one cluster without hardcoding changing IP addresses