Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1489121

Summary: Ceph pg_num and pgp_num default is too low for any user
Product: Red Hat OpenStack Reporter: jomurphy
Component: openstack-tripleo-heat-templatesAssignee: Giulio Fidente <gfidente>
Status: CLOSED ERRATA QA Contact: Yogev Rabl <yrabl>
Severity: high Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: dbecker, dcadzow, gfidente, jomurphy, mburns, morazi, rhel-osp-director-maint, tvignaud, yrabl
Target Milestone: betaKeywords: Triaged
Target Release: 12.0 (Pike)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-7.0.3-0.20171023134947.8da5e1f.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1481821 Environment:
Last Closed: 2017-12-13 22:05:43 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: 1481821    
Bug Blocks: 1489120    

Description jomurphy 2017-09-06 18:00:38 UTC
+++ This bug was initially created as a clone of Bug #1481821 +++

Description of problem:
OSP director defaults set Ceph's pg_num and pgp_num to 32 which is too low. This will cause performance issues for any costumer that will use it.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:
The pg_num and pgp_num for all the pools is 32

Expected results:
pg_num and pgp_num default should be 128, which is the right number for the minimum deployment of 3 OSDs in a cluster

Additional info:

--- Additional comment from Jeff Brown on 2017-08-29 14:11:34 EDT ---

We need to set this to 128 by default. It will potentially overwritten by derived parameters or customers that  read the documentation.

Comment 3 Yogev Rabl 2017-11-06 15:30:40 UTC
The defaults placement groups number is 128

Comment 6 errata-xmlrpc 2017-12-13 22:05:43 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/RHEA-2017:3462