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

[v24.2.x] CORE-5686 Decouple different raft group shutdown sequences #21584

Conversation

vbotbuildovich
Copy link
Collaborator

Backport of PR #21517

Added a log entry when partition is removed to make debugging partition
shutdown issues easier.

Signed-off-by: Michał Maślanka <michal@redpanda.com>
(cherry picked from commit 5f457ef)
Individual raft groups shutdown operations are not correlated and do not
need coordination with mutex. The `group_manager::_groups` vector is
always updated in synchronous parts of code therefore it do not require
the mutex either.

Removed the mutex to make shutting down different Raft groups
independent from each other.

Fixes CORE-5686

Signed-off-by: Michał Maślanka <michal@redpanda.com>
(cherry picked from commit e0236f6)
@vbotbuildovich vbotbuildovich added this to the v24.2.x-next milestone Jul 23, 2024
@vbotbuildovich vbotbuildovich added the kind/backport PRs targeting a stable branch label Jul 23, 2024
@mmaslankaprv
Copy link
Member

/ci-repeat 1

@piyushredpanda
Copy link
Contributor

#19980

@piyushredpanda piyushredpanda merged commit d433849 into redpanda-data:v24.2.x Jul 25, 2024
16 of 19 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