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'm currently deploying my distillery application to a Kubernetes cluster (v1.9.7). I have set up the headless service, configured my release with the appropriate vm.args and configured my application to set up the topology and start the cluster supervisor. I have confirmed that each of the pods created by my deployment can, in fact, ping every other pod in the deployment. I have confirmed that the DNS record for the headless service correctly resolves (indeed it appears libcluster resolves the node IPs correctly as well). However, I am still getting the following error:
It would appear that, for some reason, the VM is unable to connect to any of its peers. As I mentioned, I've verified that the network traffic is unimpeded so I'm figuring it must simply be some configuration mistake I've made but I cannot for the life of me determine what it is.
The text was updated successfully, but these errors were encountered:
Hey @dkushner,
I think there's nothing wrong with your env or nodes, there is just a typo in lib,
that's what ** (FunctionClauseError) no function clause matching in Cluster.Strategy.Kubernetes.DNS.load/1 says.
It should return just %State{} not {:noreply, %State{}}
Could you check if it's working from my PR: #76 ?
@flowerett: Aha! Yeah, the error message was pretty straightforward but I was hesitant to try and correct it directly just because I lack familiarity with the design decisions of the library.
I've just checked your fix and it works flawlessly. Thank you so much!
I'm currently deploying my distillery application to a Kubernetes cluster (v1.9.7). I have set up the headless service, configured my release with the appropriate
vm.args
and configured my application to set up the topology and start the cluster supervisor. I have confirmed that each of the pods created by my deployment can, in fact, ping every other pod in the deployment. I have confirmed that the DNS record for the headless service correctly resolves (indeed it appears libcluster resolves the node IPs correctly as well). However, I am still getting the following error:It would appear that, for some reason, the VM is unable to connect to any of its peers. As I mentioned, I've verified that the network traffic is unimpeded so I'm figuring it must simply be some configuration mistake I've made but I cannot for the life of me determine what it is.
The text was updated successfully, but these errors were encountered: