Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

emqx k8s Cluster fail to add pods #596

Open
and-dzh3 opened this issue Sep 29, 2020 · 2 comments
Open

emqx k8s Cluster fail to add pods #596

and-dzh3 opened this issue Sep 29, 2020 · 2 comments
Assignees
Labels

Comments

@and-dzh3
Copy link

Environment

  • EMQX K8S Cluster
  • emqx:v4.1.0

Description

After few Kubernetes nodes have gone and newly added, (due to running on spots instances) emqx pods go to restart loops .
Many of these logs
([email protected])1> 2020-09-28 16:04:01.021 [error] Mnesia('[email protected]'): ** ERROR ** Mnesia on '[email protected]' could not connect to node(s) ['[email protected]']

Only after recreating manually, 1 or 2 affected pods issue resolved

@terry-xiaoyu
Copy link
Member

@and-dzh3 It shows that it cannot connect to [email protected], may because the k8s network is not ready, or the node names have been changed.

@and-dzh3
Copy link
Author

@terry-xiaoyu network ready and everything looks good about Kubernetes.
I added to config EMQX_CLUSTER__AUTOHEAL: "on" looks better, but ... why auto-heal is not on by default? and why the error messages generated are not informative?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants