Bug 1644409
| Summary: | Limit pg log length during recovery/backfill so that we don't run out of memory | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Neha Ojha <nojha> |
| Component: | RADOS | Assignee: | Neha Ojha <nojha> |
| Status: | CLOSED DUPLICATE | QA Contact: | ceph-qe-bugs <ceph-qe-bugs> |
| Severity: | high | Docs Contact: | Bara Ancincova <bancinco> |
| Priority: | high | ||
| Version: | 3.1 | CC: | bancinco, ceph-eng-bugs, ceph-qe-bugs, dzafman, hnallurv, jdurgin, jquinn, kchai, kdreyer, nojha, pbyregow, vumrao |
| Target Milestone: | rc | ||
| Target Release: | 3.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
.PG log length is now limited
Previously, the `osd_max_pg_log_entries` option did not set a hard limit for the placement group (PG) log length. Consequently, during recovery and backfill, the log could grow significantly and consume a lot of memory, in some cases even all of it. With this update, a hard limit is set on the number of log entries in the PG log even during recovery and backfill.
A corner case, where it might be hard to limit the PG log length, is on erasure-coded pools, when the rollback information on some of replicas is too old for some reason.
|
Story Points: | --- |
| Clone Of: | 1608060 | Environment: | |
| Last Closed: | 2019-01-08 00:32:27 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: | 1608060, 1673654 | ||
| Bug Blocks: | |||