Bug 1569192
| Summary: | [RFE] osd: Warn about objects with too many omap entries | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Vikhyat Umrao <vumrao> |
| Component: | RADOS | Assignee: | Brad Hubbard <bhubbard> |
| Status: | CLOSED ERRATA | QA Contact: | Parikshith <pbyregow> |
| Severity: | medium | Docs Contact: | John Brier <jbrier> |
| Priority: | medium | ||
| Version: | 3.0 | CC: | agunn, bhubbard, ceph-eng-bugs, dzafman, jbrier, jdanjou, jdurgin, jraju, kchai, kdreyer, pbyregow, rperiyas |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | 3.1 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | RHEL: ceph-12.2.5-13.el7cp Ubuntu: 12.2.5-4redhat1xenial | Doc Type: | Enhancement |
| Doc Text: |
.Warnings about objects with too many omap entries
With this update to {product} warnings are displayed about pools which contain large omap objects. They can be seen in the output of `ceph health detail`. Information about the large objects in the pool are printed in the cluster logs. The settings which control when the warnings are printed are `osd_deep_scrub_large_omap_object_key_threshold` and `osd_deep_scrub_large_omap_object_value_sum_threshold`.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-26 18:19:46 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1430588, 1584264 | ||
|
Description
Vikhyat Umrao
2018-04-18 18:48:37 UTC
Upstream backport - https://github.com/ceph/ceph/pull/21518 *** Bug 1457767 has been marked as a duplicate of this bug. *** This looks fine guys, thanks. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2819 |