Bug #52537
closed
pool validation lockup on selfmanaged_snap_create()
Added by Ilya Dryomov over 2 years ago.
Updated over 2 years ago.
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.
- 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
- Backport set to pacific
- Pull request ID set to 43086
- Status changed from In Progress to Fix Under Review
- Status changed from Fix Under Review to Pending Backport
- Copied to Backport #52559: pacific: pool validation lockup on selfmanaged_snap_create() added
- 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".
Also available in: Atom
PDF