cancel
Showing results for 
Search instead for 
Did you mean: 

Noeds ACS does not connect in a cluster Hazelcast embedded in K8s cluster

brunosantos
Champ on-the-rise
Champ on-the-rise

Hi folks, 

We are deploying our Alfresco 23.2 in a cluster k8s with 2 ACS pods via helm chart.

We have activated the cluster embedded 'Hazelcast' via parameter in alfresco-global.properties: 

alfresco.cluster.enabled=true

And the port 5701 is configured in the deployment.yaml as your documentation:

ports:
- containerPort: 8080
- name: hazelcast
containerPort: 5701
protocol: TCP

Our instances show us that the cluster is active in this url: /alfresco/s/enterprise/admin/admin-clustering

But each noed has created his cluster, they are not capable of connecting to a existing cluster hazelcast.

Is there another/other properties that should be configured in alfresco-global.properties and/or helm chart files?

Thanks in advance,

Bruno Santos

1 ACCEPTED ANSWER

brunosantos
Champ on-the-rise
Champ on-the-rise

The solution was Istio (service mesh)

Istio does not allow the communication between pods via IP. To allow this operation, I had to enable the headless service on it: https://istio.io/latest/docs/ops/configuration/traffic-management/traffic-routing/#headless-services

As this exemple bellow:

https://github.com/hazelcast/hazelcast/issues/22256

View answer in original post

1 REPLY 1

brunosantos
Champ on-the-rise
Champ on-the-rise

The solution was Istio (service mesh)

Istio does not allow the communication between pods via IP. To allow this operation, I had to enable the headless service on it: https://istio.io/latest/docs/ops/configuration/traffic-management/traffic-routing/#headless-services

As this exemple bellow:

https://github.com/hazelcast/hazelcast/issues/22256