summaryrefslogtreecommitdiff
path: root/releasenotes
diff options
context:
space:
mode:
authorGorka Eguileor <geguileo@redhat.com>2022-06-22 18:47:53 +0200
committerGorka Eguileor <geguileo@redhat.com>2022-07-07 20:01:48 +0200
commit9800d58cb3e7315a1941629c3dd961cfa3b63f25 (patch)
tree4b0b32e4dc427628d50b3f4fef13c5ccaf44a12e /releasenotes
parente158ca49bee76c767ac55cf1397e13e54911fdb4 (diff)
downloadoslo-concurrency-9800d58cb3e7315a1941629c3dd961cfa3b63f25.tar.gz
Log when waiting to acquire lock
We currently have no log entry when we start trying to acquire a lock. In general this is ok, but there are cases where it can be problematic, for example if we have a deadlock situation or if a lock takes a very long time to be acquired. In those scenarios looking at the logs we would see the operation proceed normally and suddenly go completely silent without knowing that it's waiting for a lock to be freed. This patch adds a debug log message right before trying to acquire the lock so we can detect those situations. Change-Id: I1354dfb98b0927ae167802ecc4ab1d34f6b4d720
Diffstat (limited to 'releasenotes')
-rw-r--r--releasenotes/notes/log_acquiring_lock-1b224c0b1562ec97.yaml5
1 files changed, 5 insertions, 0 deletions
diff --git a/releasenotes/notes/log_acquiring_lock-1b224c0b1562ec97.yaml b/releasenotes/notes/log_acquiring_lock-1b224c0b1562ec97.yaml
new file mode 100644
index 0000000..12fd7e6
--- /dev/null
+++ b/releasenotes/notes/log_acquiring_lock-1b224c0b1562ec97.yaml
@@ -0,0 +1,5 @@
+---
+features:
+ - |
+ Log before trying to acquire a lock to help detect deadlocks and long waits
+ to acquire locks.