-
Notifications
You must be signed in to change notification settings - Fork 2k
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 rejoin_after_leave behavior #15552
Conversation
@anth0d is attempting to deploy a commit to the HashiCorp Team on Vercel. A member of the Team first needs to authorize it. |
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.
Hi @anth0d this looks great! A few remaining items:
- If you run
make cl
that'll create a changelog entry file (it should read something like "Fixed a bug where the rejoin_after_leave configuration was not respected). - This does seem like the sort of thing that could catch out users, so maybe we add a note to the version-specific upgrade guide for Nomad 1.4.4 as well. That'll be found in https://github.com/hashicorp/nomad/blob/main/website/content/docs/upgrade/upgrade-specific.mdx
- For some reason GHA didn't run on this PR, so we haven't run most of the CI testing on it. I'll try to figure that out but if you have any suggestions I'm all ears 😁
25b2fcd
to
f554364
Compare
@anth0d I think we've got the CI issue fixed. Would you mind rebasing on |
f554364
to
344d877
Compare
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.
One last docs item to fix and this will be good-to-go @anth0d!
Thanks @tgross, could you authorize the new preview app deployment? |
Co-authored-by: Tim Gross <tgross@hashicorp.com>
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.
LGTM! Thanks for sticking this out @anth0d!
Preview link for docs: https://nomad-1wafiobcv-hashicorp.vercel.app/nomad/docs/upgrade/upgrade-specific#server-rejoin_after_leave-default-false-now-enforced
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
This will effectively change the default behavior of Serf to not rejoin after leave, which (I believe...) is actually the documented behavior. But this could be perceived as a breaking change by some cluster operators who may be accustomed to server nodes ignoring leave events.
Alternative approaches which would not change the default behavior would be
nil
(not configured) from intentionallyfalse
, and default totrue
as exists todaydisable_rejoin_after_leave
which would default tofalse
and therefore continue to produce the current behaviorIn any case, docs probably need to be updated here and if necessary, a behavior change be communicated out.