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.

Sign up for GitHub

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

Jump to bottom

Call RemoveServer for reap events #5317

Merged
merged 7 commits into from
Mar 4, 2019
Merged

Call RemoveServer for reap events #5317

merged 7 commits into from
Mar 4, 2019

Commits on Feb 5, 2019

  1. Call RemoveServer for reap events 

    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 authored Feb 5, 2019
    Configuration menu
    Copy the full SHA
    495d29a View commit details
    Browse the repository at this point in the history

  2. Add test for reaping servers from the router

    @mkeeler
    mkeeler committed Feb 5, 2019
    Configuration menu
    Copy the full SHA
    c318f38 View commit details
    Browse the repository at this point in the history

Commits on Feb 8, 2019

  1. Re-Add servers for member updates.

    @mkeeler
    mkeeler authored Feb 8, 2019
    Configuration menu
    Copy the full SHA
    0337fa8 View commit details
    Browse the repository at this point in the history

Commits on Feb 28, 2019

  1. Handle EventMemberReaped and EventMemberUpdated on the LAN 

    This ensures we add/remove updated/failed servers properly.
    @mkeeler
    mkeeler committed Feb 28, 2019
    Configuration menu
    Copy the full SHA
    8bc5237 View commit details
    Browse the repository at this point in the history

  2. Add a server reap lan node test

    @mkeeler
    mkeeler committed Feb 28, 2019
    Configuration menu
    Copy the full SHA
    9357bfb View commit details
    Browse the repository at this point in the history

Commits on Mar 1, 2019

  1. Add a test for reap LAN servers from clients.

    @mkeeler
    mkeeler committed Mar 1, 2019
    Configuration menu
    Copy the full SHA
    6b0a6df View commit details
    Browse the repository at this point in the history

  2. Dont touch the EventMemberUpdate handling 

    I dont think this will cause a problem to ignore after further investigation.
    @mkeeler
    mkeeler committed Mar 1, 2019
    Configuration menu
    Copy the full SHA
    13ee12e View commit details
    Browse the repository at this point in the history