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

[v22.2.x] cluster: fix a case where version updates weren't generated #8990

Merged

Conversation

vbotbuildovich
Copy link
Collaborator

Backport of PR #8902
Fixes #8989,

Calculating deltas on health reports was not robust,
because after a leadership change theq controller can come
up on a node that already has a health report showing
a newer version, i.e. no delta wrt the next report.

Instead, generate an update to _node_versions whenever
we see a version that is newer than that in the map, and
clear _node_versions on leadership/term changes.  This
guarantees that within each controller term, we will
pay attention to node versions from all nodes until we
have accumulated a version from each node, and thereafter
we will only submit updates if the version in a health
report is newer than the one in _node_versions.

Fixes: redpanda-data#8758
(cherry picked from commit f54c7c9)
@vbotbuildovich vbotbuildovich added this to the v22.2.x-next milestone Feb 20, 2023
@vbotbuildovich vbotbuildovich added the kind/backport PRs targeting a stable branch label Feb 20, 2023
@andrwng andrwng marked this pull request as ready for review March 10, 2023 02:06
@andrwng andrwng merged commit f2a1f2e into redpanda-data:v22.2.x Mar 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/redpanda kind/backport PRs targeting a stable branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants