Bug 1552094
| Summary: | ceph-objectstore-tool command to trim the pg log | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Vikhyat Umrao <vumrao> |
| Component: | RADOS | Assignee: | David Zafman <dzafman> |
| Status: | CLOSED ERRATA | QA Contact: | Parikshith <pbyregow> |
| Severity: | urgent | Docs Contact: | Erin Donnelly <edonnell> |
| Priority: | urgent | ||
| Version: | 3.0 | CC: | ceph-eng-bugs, ceph-qe-bugs, dzafman, edonnell, hnallurv, jdurgin, kchai, kdreyer, rperiyas, tserlin |
| Target Milestone: | z2 | ||
| Target Release: | 3.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | RHEL: ceph-12.2.4-2.el7cp Ubuntu: ceph_12.2.4-3redhat1 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, an underlying issue caused the placement group (PG) log to grow without bound in certain situations. This caused OSDs to crash and stalled startup. With this release, the "trim-pg-log" operation has been added to "ceph-objectstore-tool" to allow offline trimming of large PG logs. This restores the PG log within the designated size limits.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-26 17:38:40 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: | 1557269 | ||
|
Description
Vikhyat Umrao
2018-03-06 13:47:35 UTC
The motive of this bug is to have a command to trim the pg log without consuming a lot of memory and CPU which makes the OSD node unstable. Luminous backport: http://tracker.ceph.com/issues/23275 https://github.com/ceph/ceph/pull/20803 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:1259 |