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

Checking cluster membership is not correct #31

Closed
ivanov-aleksander opened this issue Jan 20, 2020 · 1 comment
Closed

Checking cluster membership is not correct #31

ivanov-aleksander opened this issue Jan 20, 2020 · 1 comment

Comments

@ivanov-aleksander
Copy link
Contributor

ivanov-aleksander commented Jan 20, 2020

I have faced and issue with a cluster with more than 10 nodes. I have created PR 30 to fix this issue.
But I found the second issue:
The condition that checks if node already joined the cluster is not correct.
For example:

  1. Node mongooseim-10 fails to join to cluster because issue PR 30 as result pod will be restarted. But mnesia folder will be created.
  2. Next start of the node mongooseim-10 skip joining the cluster because mnesia folder exist. As a result, it will be standalone node.
@michalwski
Copy link
Contributor

Thanks for opening the issue. This is indeed a problem, I'll add this to our internal road map.

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

No branches or pull requests

3 participants