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

Call RemoveServer for reap events #5317

Merged
merged 7 commits into from
Mar 4, 2019
Merged

Conversation

mkeeler
Copy link
Member

@mkeeler mkeeler commented Feb 5, 2019

In both the leaving and reaping case the server is no longer available and therefore we must remove it from our list of servers.

If we do not remove servers for a reap event they may stay around forever until the node gets restarted.

Update: Also ensure that EventMemberUpdate events are handled just like joins to updated the server info. AddServers internally handles update vs new addition.

In both the leaving and reaping case the server is no longer available and therefore we must remove it from our list of servers.
@mkeeler mkeeler requested a review from a team February 5, 2019 20:38
@mkeeler mkeeler added this to the 1.4.3 milestone Feb 5, 2019
@mkeeler
Copy link
Member Author

mkeeler commented Feb 11, 2019

Still need to do some more digging here. There might be a LAN router problem too.

@mkeeler
Copy link
Member Author

mkeeler commented Mar 1, 2019

There definitely was a LAN router problem. In fact all 3 places that handled the serf events were wrong. The resulting behavior is that servers stuck around in our RPC routers even after they had been reaped by serf. This would persist until the node rejoined or the node was restarted.

I dont think this will cause a problem to ignore after further investigation.
Copy link
Member

@banks banks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

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

Successfully merging this pull request may close these issues.

2 participants