Actions
Bug #43455
closedToo many rgw.none indexes slow down list operations
% Done:
0%
Source:
Tags:
Backport:
mimic, nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
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
Updated by J. Eric Ivancich over 4 years ago
- Status changed from New to Fix Under Review
Updated by J. Eric Ivancich over 4 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to mimic
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #43658: mimic: Too many rgw.none indexes slow down list operations added
Updated by Nathan Cutler over 4 years ago
- Backport changed from mimic to mimic, nautilus
don't see any indication that this would not be backportable to nautilus as well (?)
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #43728: nautilus: Too many rgw.none indexes slow down list operations added
Updated by Nathan Cutler about 4 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