From 83d5438c3317e041a3f7446c9e062c2e214e60fa Mon Sep 17 00:00:00 2001
From: Martin Polden <mpolden@mpolden.no>
Date: Fri, 18 Jun 2021 14:59:36 +0200
Subject: Log when lock acquisition fails in maintenance deployment

---
 .../vespa/hosted/provision/maintenance/MaintenanceDeployment.java     | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

(limited to 'node-repository')

diff --git a/node-repository/src/main/java/com/yahoo/vespa/hosted/provision/maintenance/MaintenanceDeployment.java b/node-repository/src/main/java/com/yahoo/vespa/hosted/provision/maintenance/MaintenanceDeployment.java
index 3b16ecbcaa9..132241e711f 100644
--- a/node-repository/src/main/java/com/yahoo/vespa/hosted/provision/maintenance/MaintenanceDeployment.java
+++ b/node-repository/src/main/java/com/yahoo/vespa/hosted/provision/maintenance/MaintenanceDeployment.java
@@ -102,11 +102,13 @@ class MaintenanceDeployment implements Closeable {
     }
 
     private Optional<Mutex> tryLock(ApplicationId application, NodeRepository nodeRepository) {
+        Duration timeout = Duration.ofSeconds(1);
         try {
             // Use a short lock to avoid interfering with change deployments
-            return Optional.of(nodeRepository.nodes().lock(application, Duration.ofSeconds(1)));
+            return Optional.of(nodeRepository.nodes().lock(application, timeout));
         }
         catch (ApplicationLockException e) {
+            log.log(Level.WARNING, () -> "Could not lock " + application + " for maintenance deployment within " + timeout);
             return Optional.empty();
         }
     }
-- 
cgit v1.2.3