From 14fbad99d2c2b42158609cd107d16aef4d974beb Mon Sep 17 00:00:00 2001 From: Ilya Dryomov Date: Fri, 3 Apr 2026 18:13:01 +0200 Subject: [PATCH] doc: add RBD_LOCK_MODE_EXCLUSIVE_TRANSIENT release note I was reluctant to advertise this feature right away but it has proven to fit the bill and is getting backported to stable releases now. Signed-off-by: Ilya Dryomov --- PendingReleaseNotes | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/PendingReleaseNotes b/PendingReleaseNotes index 493307201e7..41d9d5e9358 100644 --- a/PendingReleaseNotes +++ b/PendingReleaseNotes @@ -64,7 +64,13 @@ * RBD: Mirror snapshot creation and trash purge schedules are now automatically staggered when no explicit "start-time" is specified. This reduces scheduling spikes and distributes work more evenly over time. - +* RBD: Introduced a new ``RBD_LOCK_MODE_EXCLUSIVE_TRANSIENT`` policy for + ``rbd_lock_acquire()``. This is a low-level interface intended to allow + a peer to grab exclusive lock manually for short periods of time with other + peers pausing their activity and waiting for the lock to be released rather + than instantly aborting I/O and returning an error. It's possible to switch + from ``RBD_LOCK_MODE_EXCLUSIVE`` to ``RBD_LOCK_MODE_EXCLUSIVE_TRANSIENT`` + policy and vice versa even if the lock is already held. * OSD: A health warning is reported when BlueFS usage exceeds the configured ratio of the main OSD data device size. This warning is informational and can be muted with: -- 2.47.3