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
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
The text was updated successfully, but these errors were encountered:
@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?
Environment
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
The text was updated successfully, but these errors were encountered: