From: Niklas Hambüchen Date: Sun, 10 May 2026 03:35:52 +0000 (+0000) Subject: docs: balancer: Explain limitations of PG shard count balancing X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=8f83ec546aa16c3e06f1a2b1cbf4c8f657771f55;p=ceph.git docs: balancer: Explain limitations of PG shard count balancing Signed-off-by: Niklas Hambüchen --- diff --git a/doc/rados/operations/balancer.rst b/doc/rados/operations/balancer.rst index a797f9be205..bfd37a10aa4 100644 --- a/doc/rados/operations/balancer.rst +++ b/doc/rados/operations/balancer.rst @@ -39,6 +39,22 @@ combines the upmap balancer with the read balancer so that both writes and reads are optimized. ``read`` mode can be used when only read optimization is desired. For more details, see :ref:`read_balancer`. +Limitation: count-based balancing vs. size-based balancing +---------------------------------------------------------- + +Ceph's built-in balancer optimizes only by **PG shard count**, not by the +actual size of the data stored in each PG. + +This can result in clusters whose OSDs are balanced by PG shard count, +but very imbalanced by stored Bytes. +At the pool level, this can cause a pool's ``%USED`` (from ``ceph df``) +to be much higher than the cluster's ``%RAW USED``, because the +pool's fullest OSD (which determines the pool's available space) may be +disproportionately loaded with large PGs. + +Size-aware community balancers exist (for example, +`jj-balancer `_). + Throttling ----------