-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Fix/1160 fix clustering #1437
Fix/1160 fix clustering #1437
Conversation
@asknaskan it seems like there are unresolved conflicts |
# Conflicts: # kong/cli/services/serf.lua
@thefosk Well, I noticed a bit late I'm being at master code base. I created something similar on the next code base. The next branch version is not working at the vagrant kong, so I have to wait for checks - But it should fit. |
Look's like there is a lot of stuff broken at the moment, so the checks failed. I'm not be able to start an kong on next branch (docker) at the moment. If you want to, please try to test it. |
@@ -92,6 +92,9 @@ function _M.start(kong_config, dao) | |||
return nil, "could not start Serf: "..err | |||
end | |||
|
|||
-- cleanup current node from cluster to prevent inconsistency of data | |||
serf:cleanup() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@asknaskan can you please check for errors here?
local ok, err = serf:cleanup()
if not ok then return nil, err end
Summary
I just changed the position of inconsistency check from clustering to prevent that an node removes itself if it failed to cluster.
Instead of checking it when joining an cluster, I now check it when starting the node.
Full changelog
Issues resolved
Fix #1160