PendingReleaseNotes: document online and offline trimming of PG Log's dups

Signed-off-by: Radoslaw Zarzynski <rzarzyns@redhat.com>
(cherry picked from commit dbfb50453c2f7fe5b0a06d846dd38693cceb63fe)

Conflicts:
    PendingReleaseNotes
- Moved the note under ">=17.2.4" section

diff --git a/PendingReleaseNotes b/PendingReleaseNotes
index 873c3e7ca18c5360e738d1b8ba5403d300365607..53447bf4c2153aebf524c3780c54f538b50de479 100644 (file)
--- a/PendingReleaseNotes
+++ b/PendingReleaseNotes
@@ -8,6 +8,15 @@
 * OSD: The issue of high CPU utilization during recovery/backfill operations
   has been fixed. For more details, see: https://tracker.ceph.com/issues/56530.
 
+* Trimming of PGLog dups is now controlled by the size instead of the version.
+  This fixes the PGLog inflation issue that was happening when the on-line
+  (in OSD) trimming got jammed after a PG split operation. Also, a new off-line
+  mechanism has been added: `ceph-objectstore-tool` got `trim-pg-log-dups` op
+  that targets situations where OSD is unable to boot due to those inflated dups.
+  If that is the case, in OSD logs the "You can be hit by THE DUPS BUG" warning
+  will be visible.
+  Relevant tracker: https://tracker.ceph.com/issues/53729
+
 >=17.2.1
 
 * The "BlueStore zero block detection" feature (first introduced to Quincy in