Bug 1947215 - [GSS] bluestore scrub memory growth due to low bluestore_cache_trim_max_skip_pinned
Summary: [GSS] bluestore scrub memory growth due to low bluestore_cache_trim_max_skip_...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 4.2
Hardware: All
OS: Linux
high
high
Target Milestone: ---
: 4.2z2
Assignee: Neha Ojha
QA Contact: skanta
Amrita
URL:
Whiteboard:
Depends On: 1931504
Blocks: 1890121
TreeView+ depends on / blocked
 
Reported: 2021-04-07 23:23 UTC by Neha Ojha
Modified: 2021-06-15 17:14 UTC (History)
19 users (show)

Fixed In Version: ceph-14.2.11-157.el8cp, ceph-14.2.11-157.el7cp
Doc Type: Bug Fix
Doc Text:
.Memory growth because of onodes is now controlled Previously, the default value for the option `bluestore_cache_trim_max_skip_pinned` was 64 which was very low for large clusters. Since this option controlled the rate of trimming onodes and with current default value, it could have led to a buildup of onodes causing memory growth. With this release, the default value of bluestore_cache_trim_max_skip_pinned` is 1000 and the memory growth is controlled.
Clone Of: 1931504
Environment:
Last Closed: 2021-06-15 17:13:47 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph pull 40920 0 None open nautilus: common/options/global.yaml.in: increase default value of bluestore_cache_trim_max_skip_pinned 2021-04-19 17:45:56 UTC
Red Hat Product Errata RHSA-2021:2445 0 None None None 2021-06-15 17:14:03 UTC

Comment 13 errata-xmlrpc 2021-06-15 17:13:47 UTC 
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 (Important: Red Hat Ceph Storage 4.2 Security and Bug Fix Update), 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/RHSA-2021:2445
Note You need to log in before you can comment on or make changes to this bug.