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

Master collision never resolved #147

Open
kaabar opened this issue May 6, 2019 · 0 comments
Open

Master collision never resolved #147

kaabar opened this issue May 6, 2019 · 0 comments

Comments

@kaabar
Copy link

kaabar commented May 6, 2019

Hello,
When a master node hang for while and new master has been elected for the group, if the old master node is able restore itself then it will start a collision resolving with the current new master, this process never ends and go on for ever as both nodes insist on becoming master.
The problem is likely related to line number 1007
if (madv.getID().compareTo(adv.getID()) >= 0)
The test here does not much the check done in checkMaster mothod at line 249
if (isSeniorMember(manager.getSystemAdvertisement(), systemAdv))

I this both method should have the same check which is isSeniorMember

You can reproduce the issue by suspending the gms threads in the master node untill a new master is elected, and the resume, you will notice the infinite messsage exchange between two masters

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

1 participant