Hazelcast connection

General
, , , ,
1

Hello,

Below is what we see as the recommended setting in the documentation for connecting to clustering service from pega nodes. We are trying to externalize the backing services. Hazelcast is deployed externally on EKS. We are trying to connect to this clustering service from a VM Based deployment (beanstalk).

Is there a way to specify the service(K8S) DNS Name instead of the ips here in this setting below to facilitate connectivity?

If so, what are pre-requisites if any for this connectivity to work as expected?

<env name="cluster/clientserver/serveraddress" value="ipOfHazelcastServer1:port,ipOfHazelcastServer2:port,ipOfHazelcastServer3:port" />
2

@SethuS88 Below is our GenAI response:

you can specify the service (K8S) DNS Name instead of the IPs in the prconfig.xml file for connecting to the Hazelcast clustering service from a VM based deployment. To configure this you need to set the hazelcast/external/members environment variable with the DNS names. Here is an example configuration: xml env name

:warning: This is a GenAI-powered tool. All generated answers require validation against the provided references.

External Hazelcast in your deployment

Connecting to your managed Hazelcast service

Known Issues with Embedded Hazelcast Deployments

Troubleshooting Hazelcast cluster management

3

@MarijeSchillern I don’t see any setting like hazelcast/external/members in the links you provided below.

You mentioned “Here is an example”. However I don’t see any relevant attachments that shows this example. Can you provide the attachment? Also, the comment you provided was based on the assumption that hazelcast was deployed using the war file or is the sample relevant to pega clusters running externally(on VMs through VM Based deployment model) connecting to hazelcast running on EKS?

Here are my questions. Can you provide your response for the below?

  1. We are trying to connect our pega nodes running outside of EKS(on VM – Elastic Beanstalk) to hazelcast service running on EKS.
  2. The documentation supports connecting to the clustering service only via IP. We tried using the Load balancer IP(for the Service running on EKS) that is exposed for this connection and it didn’t work as expected.
  3. I have attached the cluster logs and pega rules log to the ticket.
  4. Earlier, we tried using the DNS(for the load balancer) to connect to the service and it didn’t work either
  5. We want to know 1) If we can connect to the hazelcast/clustering service if the pega nodes are running outside of EKS or whether it can be connected to only from within the K8S Cluster? 2) If we can use the DNS instead of IPs since DNS has a higher level of abstraction and we don’t have to worry about Pods getting replaced(in which case the IP will change) – This question is applicable for both (hybrid mode and also if both pega as well as the clustering service is running on the same cluster).
4

@SethuS88 I have checked internally and I believe your question is more complex than can be covered in a forum post. There are usually more issues that come up when dealing with one hypothetical scenario at a time.

The advice given was that you should contact your AE to discuss engaging a Deployment Architect from our Deployment Services team.

If in the meantime anyone else can comment further please feel free to do so.

@SriHarsha Anika @KOHNF can someone from your teams help with this question?