Actions
Bug #52698
closedcrimson assert happened in SegmentCleaner
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
src/crimson/os/seastore/segment_cleaner.h:880 : In function 'seastar::future<> crimson::os::seastore::SegmentCleaner::await_hard_limits()', ceph_assert(%s)
!blocked_io_wake
Updated by Samuel Just over 2 years ago
await_hard_limits() has the following:
// The pipeline configuration prevents another IO from entering
// prepare until the prior one exits and clears this.
ceph_assert(!blocked_io_wake);
The comment is no longer true. I think when I swapped the pipelining to permit concurrent transaction submission (prior to prepare) for different collections, I broke this constraint without noticing. Should be a pretty simple fix.
Actions