Bug 1633426 - RHCS 3.2 - increase mon_max_pg_per_osd to 250
Summary: RHCS 3.2 - increase mon_max_pg_per_osd to 250
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 3.2
Hardware: x86_64
OS: Linux
low
high
Target Milestone: rc
: 3.2
Assignee: Josh Durgin
QA Contact: ceph-qe-bugs
Bara Ancincova
URL:
Whiteboard:
Depends On: 1597425
Blocks: 1629656
TreeView+ depends on / blocked
 
Reported: 2018-09-27 00:32 UTC by Josh Durgin
Modified: 2021-12-10 17:50 UTC (History)
13 users (show)

Fixed In Version: RHEL: ceph-12.2.8-3.el7cp Ubuntu: ceph_12.2.8-3redhat1
Doc Type: Bug Fix
Doc Text:
.PGs per OSD limits have been increased In some situations, such as widely varying disk sizes, the default limit on placement groups (PGs) per OSD could prevent PGs from going active. These limits have been increased by default to make this situation less likely.
Clone Of: 1597425
Environment:
Last Closed: 2019-01-03 19:01:53 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 24356 0 None None None 2018-09-27 00:32:08 UTC
Github ceph ceph pull 22592 0 None closed luminous: osd: increase default hard pg limit 2021-02-03 12:14:25 UTC
Github ceph ceph pull 23862 0 None closed luminous: core: osd,mon: increase mon_max_pg_per_osd to 250 2021-02-03 12:14:25 UTC
Red Hat Issue Tracker RHCEPH-2720 0 None None None 2021-12-10 17:50:11 UTC
Red Hat Knowledge Base (Solution) 3526531 0 None None None 2018-09-27 00:32:08 UTC
Red Hat Product Errata RHBA-2019:0020 0 None None None 2019-01-03 19:02:06 UTC

Comment 10 errata-xmlrpc 2019-01-03 19:01:53 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, 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-2019:0020
Note You need to log in before you can comment on or make changes to this bug.