Comment 7 for bug 1492742

Hi Brian, bumping the max pg limit is not ideal since it is masking what could be a real problem. Having too many PGs can result in performance degradation due to the extra system resources consumed by Ceph in order to manage those PGs. Unfortunately Ceph does not allow you do reduce the number of PGs in a pool so adding more OSDs is the only real solutions here. Having said that I think we should add support to the charm for defining a capped/max number of PGs that will be assigned at deploy time and leave adjustment to post-deploy time (perhaps using an action to tune the PG count of pools).