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

CORE-5686 Decouple different raft group shutdown sequences #21517

Merged
merged 2 commits into from
Jul 22, 2024

Conversation

mmaslankaprv
Copy link
Member

@mmaslankaprv mmaslankaprv commented Jul 19, 2024

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

Backports Required

  • none - not a bug fix
  • none - this is a backport
  • none - issue does not exist in previous branches
  • none - papercut/not impactful enough to backport
  • v24.1.x
  • v23.3.x
  • v23.2.x

Release Notes

  • none

@vbotbuildovich
Copy link
Collaborator

vbotbuildovich commented Jul 19, 2024

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

Signed-off-by: Michał Maślanka <michal@redpanda.com>
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>
@mmaslankaprv mmaslankaprv merged commit 5496b70 into redpanda-data:dev Jul 22, 2024
19 checks passed
@mmaslankaprv mmaslankaprv deleted the fix-CORE-5686 branch July 22, 2024 10:17
@vbotbuildovich
Copy link
Collaborator

/backport v24.1.x

@vbotbuildovich
Copy link
Collaborator

/backport v23.3.x

@vbotbuildovich
Copy link
Collaborator

Failed to create a backport PR to v24.1.x branch. I tried:

git remote add upstream https://github.com/redpanda-data/redpanda.git
git fetch --all
git checkout -b backport-pr-21517-v24.1.x-165 remotes/upstream/v24.1.x
git cherry-pick -x 5f457ef851d9f733a37cf82b0fc1109856a38e19 e0236f68e22206d9a81a19124b1c71b808870115

Workflow run logs.

@vbotbuildovich
Copy link
Collaborator

Failed to create a backport PR to v23.3.x branch. I tried:

git remote add upstream https://github.com/redpanda-data/redpanda.git
git fetch --all
git checkout -b backport-pr-21517-v23.3.x-620 remotes/upstream/v23.3.x
git cherry-pick -x 5f457ef851d9f733a37cf82b0fc1109856a38e19 e0236f68e22206d9a81a19124b1c71b808870115

Workflow run logs.

@mmaslankaprv
Copy link
Member Author

/backport v24.2.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants