Bug #43455
closed
Too many rgw.none indexes slow down list operations
Added by Ilsoo Byun over 4 years ago.
Updated about 4 years ago.
Description
I don't know why rgw.none indexes are created so much.
To my knowledge, rgw.none index is generated when cancelling a rgw transaction.
I just assume that multiple LC processes would try to delete the same object simultaneously.
Anyway, whatever the reason is, in this situation, a list operation takes too much time to complete.
Looking at the log, it seems like it's stuck in an infinite loop.
The same keys appear multiple times.
Files
- Assignee set to J. Eric Ivancich
- Pull request ID set to 32513
- Status changed from New to Fix Under Review
- Status changed from Fix Under Review to Pending Backport
- Backport set to mimic
- Copied to Backport #43658: mimic: Too many rgw.none indexes slow down list operations added
- Backport changed from mimic to mimic, nautilus
don't see any indication that this would not be backportable to nautilus as well (?)
- Copied to Backport #43728: nautilus: Too many rgw.none indexes slow down list operations 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
