Actions
Bug #52537
closedpool validation lockup on selfmanaged_snap_create()
% Done:
0%
Source:
Tags:
Backport:
pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Description
Concurrent rbd_pool_init() or rbd_create() operations on an unvalidated (uninitialized) pool trigger a lockup in ValidatePoolRequest state machine caused by blocking selfmanaged_snap_{create,remove}() calls.
There are two reactor threads by default (librados_thread_count) but we effectively need N + 1 reactor threads for N concurrent pool validation requests, especially for small N.
Updated by Ilya Dryomov over 2 years ago
- Subject changed from pool validation lockup to pool validation lockup on selfmanaged_snap_create()
- Description updated (diff)
- Status changed from New to In Progress
- Assignee set to Ilya Dryomov
Updated by Ilya Dryomov over 2 years ago
- Backport set to pacific
- Pull request ID set to 43086
Updated by Ilya Dryomov over 2 years ago
- Status changed from In Progress to Fix Under Review
Updated by Ilya Dryomov over 2 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot over 2 years ago
- Copied to Backport #52559: pacific: pool validation lockup on selfmanaged_snap_create() added
Updated by Loïc Dachary over 2 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions