PendingReleaseNotes: update release notes

Update the pending release notes explaining
why we are making the autoscaler profile
`scale-up` by default.

Signed-off-by: Kamoltat <ksirivad@redhat.com>

diff --git a/PendingReleaseNotes b/PendingReleaseNotes
index 4bbf36c37b45e1329788e2efafcfb2819d8eb518..75b50b45e5633d26c29dce3de414529ea2257143 100644 (file)
--- a/PendingReleaseNotes
+++ b/PendingReleaseNotes
@@ -41,12 +41,19 @@
   quick-fix/repair commands are invoked.
   Relevant tracker: https://tracker.ceph.com/issues/53062
 
+* MGR: The pg_autoscaler will use the 'scale-up' profile as the default profile.
+  16.2.6 changed the default profile to 'scale-down' but we ran into issues
+  with the device_health_metrics pool consuming too many PGs, which is not ideal
+  for performance. So we will continue to use the 'scale-up' profile by default,
+  until we implement a limit on the number of PGs default pools should consume,
+  in combination with the 'scale-down' profile.
+
 >=16.2.6
 --------
 
-* MGR: The pg_autoscaler has a new 'scale-down' profile which provides more
-  performance from the start for new pools. However, the module will remain
-  using it old behavior by default, now called the 'scale-up' profile.
+* MGR: The pg_autoscaler has a new default 'scale-down' profile which provides more
+  performance from the start for new pools (for newly created clusters).
+  Existing clusters will retain the old behavior, now called the 'scale-up' profile.
   For more details, see:
 
   https://docs.ceph.com/en/latest/rados/operations/placement-groups/