Actions
Bug #45970
closedrgw: bucket index entries marked rgw.none not accounted for correctly during reshard
% Done:
0%
Source:
Tags:
Backport:
octopus,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
If we reshard versioning bucket, bucket stats will contain extra information `rgw.none`.
Before reshard:
"mtime": "2019-07-16T09:39:07.175539Z", "max_marker": "0#,1#,2#", "usage": { "rgw.main": { "size": 2, "size_actual": 4096, "size_utilized": 2, "size_kb": 1, "size_kb_actual": 4, "size_kb_utilized": 1, "num_objects": 1 } },
After reshard:
"mtime": "2019-07-17T02:36:12.490795Z", "max_marker": "0#,1#,2#,3#,4#", "usage": { "rgw.none": { "size": 0, "size_actual": 0, "size_utilized": 0, "size_kb": 0, "size_kb_actual": 0, "size_kb_utilized": 0, "num_objects": 1 }, "rgw.main": { "size": 2, "size_actual": 4096, "size_utilized": 2, "size_kb": 1, "size_kb_actual": 4, "size_kb_utilized": 1, "num_objects": 1 } },
Versioning bucket has idx like below and it's counted in stats while resharding bucket.
"type": "plain", "idx": "obj10", "entry": { "name": "obj10", "instance": "", "ver": { "pool": -1, "epoch": 0 }, "locator": "", "exists": "false", "meta": { "category": 0, "size": 0, "mtime": "0.000000", "etag": "", "storage_class": "", "owner": "", "owner_display_name": "", "content_type": "", "accounted_size": 0, "user_data": "", "appendable": "false" }, "tag": "", "flags": 8, "pending_map": [], "versioned_epoch": 0 }
Updated by J. Eric Ivancich almost 4 years ago
- Status changed from New to Pending Backport
Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #46004: nautilus: rgw: bucket index entries marked rgw.none not accounted for correctly during reshard added
Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #46005: octopus: rgw: bucket index entries marked rgw.none not accounted for correctly during reshard added
Updated by Casey Bodley almost 4 years ago
- Related to Bug #46400: Space usage accounting overestimated added
Updated by Nathan Cutler almost 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