* Description of problem: If the number of objects per PG is more, then we will get an error "Too many objects per pg than average". The warning is an attempt to warn when pools are very unbalanced. Most clusters have mostly the same-sized objects in them but if the amount of data is matching and the object count isn't for different pools, we either need the warning to be more useful, like how it will negatively affect the cluster performance or everything's good to keep as it is. There is also no information regarding objects per PG while calculating the PG count in PG Calc, which creates ambiguity as in whether the warning should really be taken into consideration. * Version-Release number of selected component (if applicable): Red Hat Ceph Storage 3.0 * How reproducible: Always * Steps to Reproduce: NA * Actual results: * Expected results: * Additional info:
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri
The pg_autoscaler in octopus makes this obsolete.