Actions
Feature #41359
closedAdding Placement Group id in Large omap log message
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Administration/Usability
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
nautilus, mimic, luminous
Reviewed:
Description
2019-08-20 00:16:26.354331 osd.13 osd.13 192.168.42.218:6804/725336 469 : cluster [WRN] Large omap object found. Object: 272:77fe05db:::.dir.7659bed4-dcd2-4616-95b3-4f7d971c6dd8.2907365.1:head Key count: 2401160 Size (bytes): 459802197
Adding the pg id will help to avoid the following step.
ceph osd map site1.rgw.buckets.index .dir.7659bed4-dcd2-4616-95b3-4f7d971c6dd8.2907365.1 osdmap e7749 pool 'site1.rgw.buckets.index' (272) object '.dir.7659bed4-dcd2-4616-95b3-4f7d971c6dd8.2907365.1' -> pg 272.dba07fee (272.6e) -> up ([13,4,60], p13) acting ([13,4,60], p13)
Updated by Brad Hubbard over 4 years ago
- Status changed from New to In Progress
- Backport set to nautilus, mimic, luminous
Updated by Neha Ojha over 4 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 30682
Updated by Brad Hubbard over 4 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42240: mimic: Adding Placement Group id in Large omap log message added
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42241: luminous: Adding Placement Group id in Large omap log message added
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42242: nautilus: Adding Placement Group id in Large omap log message added
Updated by Yuri Weinstein over 4 years ago
Updated by Nathan Cutler over 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