kv/RocksDBStore: Remove ability to bound WholeSpaceIterator#46095
kv/RocksDBStore: Remove ability to bound WholeSpaceIterator#46095yuriw merged 1 commit intoceph:masterfrom
Conversation
…ounded iterator Iterator-bounding feature is introduced to make RocksDB iterators limited, so they would less likely traverse over tombstones. This is used when listing keys in fixed range, for example OMAPS for specific object. It is problematic when extending this logic to WholeSpaceIterator, since prefix must be taken into account. Fixes: https://tracker.ceph.com/issues/55444 Signed-off-by: Adam Kupczyk <akupczyk@redhat.com>
c0bdd4d to
6b9b938
Compare
6b9b938 to
4983708
Compare
4983708 to
6b9b938
Compare
idryomov
left a comment
There was a problem hiding this comment.
This fixes it for my TestClsJournal upgrade reproducer as well, so +1.
However I'm concerned about the lack of a straightforward automated test here. Since you found a way to reproduce without involving the upgrade suite (which is cumbersome to run on custom branches for debugging and can be a bit challenging to interpret as well), should a new workunit that would stand up the cluster with
bluestore_rocksdb_cfs="M= P= L="
bluestore_rocksdb_cf=false
and run basic omap tests be added to the rados suite?
I intent to add:
|
|
@aclamk Yuri reported the following failure in the tracker ticket. Not sure if it is related to the original bound iterators change, PTAL: |
|
@idryomov that looks like https://tracker.ceph.com/issues/52590#note-5. there was an API-breaking bug fix in 16.2.6, so upgrades from 16.2.5 are expected to fail there |
|
Oh, I see -- I have to confess to not searching the tracker for this one as the failure seemed to point in the same general direction at first glance. No further concerns from me then! |
neha-ojha
left a comment
There was a problem hiding this comment.
Test results look good - http://pulpito.front.sepia.ceph.com/?branch=wip-yuri3-testing-2022-04-29-1830
Iterator-bounding feature is introduced to make RocksDB iterators limited, so they
would less likely traverse over tombstones.
This is used when listing keys in fixed range, for example OMAPS for specific object.
It is problematic when extending this logic to WholeSpaceIterator,
since prefix must be taken into account.
Fixes: https://tracker.ceph.com/issues/55444
Replication:
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "pacific"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windows