Hmmm, I thought this was fixed by Squid. I've seen Pool wombats has 32 placement groups, should have 32 with Pacific. I might suggest either enabling the autoscaler or setting the mode to off. When enabling, setting mon_max_pg_per_osd 500 mon_target_pg_per_osd 300 will likely give you reasonable results.

On Apr 16, 2026, at 10:07 AM, Sascha Lucas via ceph-users <ceph-users@ceph.io> wrote:

Hi,

having a small ceph-19.2.3 cluster for RGW workload. index-pool is on separate SSD class. PG autoscaler is enabled in warning mode only.

Cluster health is:

# ceph health detail HEALTH_WARN 1 pools have too many placement groups [WRN] POOL_TOO_MANY_PGS: 1 pools have too many placement groups Pool default.rgw.buckets.index has 64 placement groups, should have 32

When merging PGs down to 32, the opposite is shown:

# ceph health detail HEALTH_WARN 1 pools have too few placement groups [WRN] POOL_TOO_FEW_PGS: 1 pools have too few placement groups Pool default.rgw.buckets.index has 32 placement groups, should have 64

It seems not the autoscaler who raises health warning here (NEW PG_NUM is empty):

# ceph osd pool autoscale-status POOL SIZE TARGET SIZE RATE RAW CAPACITY RATIO TARGET RATIO EFFECTIVE RATIO BIAS PG_NUM NEW PG_NUM AUTOSCALE BULK .mgr 23812k 3.0 384.0G 0.0002 1.0 1 warn False .rgw.root 20480 3.0 384.0G 0.0000 1.0 32 warn False default.rgw.log 23905k 3.0 384.0G 0.0002 1.0 32 warn False default.rgw.control 0 3.0 384.0G 0.0000 1.0 32 warn False default.rgw.meta 575.2k 3.0 384.0G 0.0000 4.0 32 warn False default.rgw.buckets.index 3017M 3.0 384.0G 0.0230 4.0 64 warn False default.rgw.buckets.non-ec 0 3.0 384.0G 0.0000 1.0 32 warn False default.rgw.buckets.data 10678G 3.0 374.2T 0.0836 1.0 1024 warn True

Anyone knowing from where this health warning is coming and how to stop the ping-pong?

Thanks, Sascha. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io