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

[v23.3.x] config: update bindings when properties are reset #16638

Conversation

vbotbuildovich
Copy link
Collaborator

Backport of PR #16504

Previously, the max_connections_per_ip watch callback assumed that if
there are overrides present, the main per-ip limit is there as well.

(cherry picked from commit 30309ea)
Remove an old way of setting the property value that was only used in
tests.

(cherry picked from commit bb6e9b4)
Previously, if one of the binding watch callbacks threw an exception,
the main property value didn't get updated, resulting in an
inconsistency.

(cherry picked from commit d58fe3d)
Previously we just set the value without notifying bindings. This
lead to ignoring property value updates when the property was reset to
its default value as a result of a patch_cluster_config request
with non-empty "remove" section.

(cherry picked from commit 7411586)
@vbotbuildovich vbotbuildovich added this to the v23.3.x-next milestone Feb 19, 2024
@vbotbuildovich vbotbuildovich added the kind/backport PRs targeting a stable branch label Feb 19, 2024
@piyushredpanda piyushredpanda modified the milestones: v23.3.x-next, v23.3.6 Feb 19, 2024
@piyushredpanda piyushredpanda merged commit 361ed48 into redpanda-data:v23.3.x Feb 20, 2024
17 checks passed
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