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

Backport of autopilot: include only servers from the same region into release/1.4.x #15292

Conversation

hc-github-team-nomad-core
Copy link
Contributor

Backport

This PR is auto-generated from #15290 to be assessed for backporting due to the inclusion of the label backport/1.4.x.

The below text is copied from the body of the original PR.


Fixes #15085

When we migrated to the updated autopilot library in Nomad 1.4.0, the interface for finding servers changed. Previously autopilot would get the serf members and call IsServer on each of them, leaving it up to the implementor to filter out clients (and in Nomad's case, other regions). But in the "new" autopilot library, the equivalent interface is KnownServers for which we did not filter by region. This causes spurious attempts for the cross-region stats fetching, which results in TLS errors and a lot of log noise.

Filter the member set by region to fix the regression.


Compare old caller (in Consul, which we imported directly): autopilot.go#L215
vs new caller (in the library): reconcile.go#L180

@hc-github-team-nomad-core hc-github-team-nomad-core merged commit 66d4c88 into release/1.4.x Nov 17, 2022
@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/autopilot-cross-region/wildly-thorough-sloth branch from f9af325 to 1dfc49c Compare November 17, 2022 17:12
@hc-github-team-nomad-core hc-github-team-nomad-core deleted the backport/autopilot-cross-region/wildly-thorough-sloth branch November 17, 2022 17:12
@github-actions
Copy link

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.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants