Cluster discovery for Hazelcast clients - Nomad and Consul on VMs in Azure #23207
Unanswered
wclark-accela
asked this question in
Q&A
Replies: 1 comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have configured a Hazelcast cluster in Azure and am looking for help on how to configure the clients for auto-join.
Each cluster member is deployed via docker using Hashicorp's Nomad and Consul service mesh tools. Auto-discovery using an Azure tag on the network interface works great.
However, each cluster member only binds to the Azure private IP of the VM where it's running, not localhost/127.0.0.1.
Is it possible to configure the clients to discover the cluster members as well, or at least the cluster member running on the same VM?
All clients are dockerized Java Spring apps also deployed using Nomad/Consul.
Beta Was this translation helpful? Give feedback.
All reactions