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] cloud_storage_clients/client_pool: handle broken _self_config_barrier #16401

Conversation

vbotbuildovich
Copy link
Collaborator

Backport of PR #16385

_self_config_barrier is a semaphore used as a barrier for the self
config step.

at shutdown_connections/stop it's broken (like it's done for _cvar the
condition_variable), so it's not useful to bubble up the
broken_named_semaphore exception.

the code after this will convert it to a gate_closed_exception

(cherry picked from commit ef9af44)
these silence broken_named_semaphore generated by client_pool::acquire.
since this exception is handled locally there, they are not needed
anymore

(cherry picked from commit 7f1bee8)
@vbotbuildovich vbotbuildovich added this to the v23.3.x-next milestone Jan 31, 2024
@vbotbuildovich vbotbuildovich added the kind/backport PRs targeting a stable branch label Jan 31, 2024
@piyushredpanda piyushredpanda merged commit 005add8 into redpanda-data:v23.3.x Feb 3, 2024
16 of 18 checks passed
@piyushredpanda piyushredpanda modified the milestones: v23.3.x-next, v23.3.5 Feb 7, 2024
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