You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two Kubernetes clusters. I have created hazelcast-cluster with members A,B,C in East AKS cluster and hazelcast-cluster with members D,E,F in West AKS cluster. Now I want A,B,C to discover D,E,F. How can I do that?
#285
Both Kubernetes clusters are in different network. I saw this #141 but it has been closed. So I was looking for a solution other than using hazelcast enterprise feature or having one AKS cluster in two regions.
The text was updated successfully, but these errors were encountered:
So you'd like to have one Hazelcast cluster stretched across multiple Kubernetes clusters, right?
Technically, you could do it by using host network or host port (but it's not a recommended approach). Also, if you have one Hazelcast cluster across multiple regions, the performance will be terrible, so you shouldn't do it at all.
The proper way to do it is to have 2 separate Hazelcast cluster with the WAN replication in between. WAN, however is an enterprise feature. If you're interested more in WAN, please check this guide: https://guides.hazelcast.org/kubernetes-wan/.
@leszko I am pretty much naive with Hazelcast. Going for enterprise feature is not an option for me.
So please explain more on using host network ( I tried TCP/IP discovery strategy but it didn't work)
Please tell does the below approach can work?
Have two clients( one in the East Region and one in the West Region) for each Hazelcluster.
Now let's assume I have East Hazelcast cluster ( members A, B, C) and one hazelcast client (Client X) in the East region.
Similarly, I have West Hazelcast cluster ( members D, E, F) and one hazelcast client (Client Y) in the west region.
Now, can Client X or Y get/put data in East Hazelcast Cluster as well as West Hazelcast Cluster using client REST API?
Both Kubernetes clusters are in different network. I saw this #141 but it has been closed. So I was looking for a solution other than using hazelcast enterprise feature or having one AKS cluster in two regions.
The text was updated successfully, but these errors were encountered: