Bug 1489064

Summary: prevent creation (of pools with) too many PGs
Product: Red Hat Ceph Storage Reporter: Sage Weil <sweil>
Component: RADOSAssignee: Josh Durgin <jdurgin>
Status: CLOSED ERRATA QA Contact: shylesh <shmohan>
Severity: high Docs Contact: Bara Ancincova <bancinco>
Priority: high    
Version: 3.0CC: ceph-eng-bugs, ceph-qe-bugs, dzafman, hnallurv, icolle, jdurgin, kchai, kdreyer, mhackett, shmohan, sweil, tserlin, vumrao
Target Milestone: rcKeywords: Reopened
Target Release: 3.0   
Hardware: All   
OS: All   
Fixed In Version: RHEL: ceph-12.2.1-16.el7cp Ubuntu: ceph_12.2.1-18redhat1 Doc Type: Bug Fix
Doc Text:
.The number of PGs per OSD is now limited Previously, it was possible to create pools that included a large number of placement groups (PGs) which could overload the cluster. This update introduces a new configuration option, `mon_max_pg_per_osd`, that limits the number of PGs per OSD to 200. Creating pools or adjusting the `pg_num` parameter now fails if the change would make the number of PGs per OSD exceed the configured limit. You can adjust this option in the Ceph configuration file. In addition, the `mon_pg_warn_max_per_osd` option has been removed.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-05 23:42:05 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:
Bug Depends On:    
Bug Blocks: 1494421    

Description Sage Weil 2017-09-06 15:59:30 UTC
Description of problem:

Users can create pools with lots of pgs and overload the cluster.  Prevent that via a config option that limits the pgs per osd.

See upstream PR https://github.com/ceph/ceph/pull/17427.  This will need to be backported to luminous and (maybe) 2.y.

Comment 2 Ian Colle 2017-10-04 15:31:08 UTC
https://github.com/ceph/ceph/pull/17814 is backport PR

Comment 6 Josh Durgin 2017-10-16 15:20:31 UTC

*** This bug has been marked as a duplicate of bug 1491007 ***

Comment 8 Josh Durgin 2017-10-16 15:30:00 UTC
*** Bug 1491007 has been marked as a duplicate of this bug. ***

Comment 18 shylesh 2017-10-25 09:28:03 UTC
Verified on 12.2.1-29

Comment 22 errata-xmlrpc 2017-12-05 23:42:05 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.