From ea7a7e7cf9697850f17631f79ef4ef45b95c449e Mon Sep 17 00:00:00 2001 From: Adam Kasztenny Date: Sat, 14 Mar 2026 16:51:49 -0400 Subject: [PATCH] Reduce log level for optimistic lease update fallback The "Failed to update lease optimistically, falling back to slow path" message was logged at Error level, but this is expected behavior during normal leader election when the optimistic update encounters a conflict. The system gracefully falls back to the slow path (Get + Update), so this is not a real error. Downgrade to V(2) Info to reduce log noise. Kubernetes-commit: 04977a0ea4592bfaa70d5095a4cfe99dd4b847e1 --- tools/leaderelection/leaderelection.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/leaderelection/leaderelection.go b/tools/leaderelection/leaderelection.go index f37bcaf27..00798d82a 100644 --- a/tools/leaderelection/leaderelection.go +++ b/tools/leaderelection/leaderelection.go @@ -451,7 +451,7 @@ func (le *LeaderElector) tryAcquireOrRenew(ctx context.Context) bool { le.setObservedRecord(&leaderElectionRecord) return true } - logger.Error(err, "Failed to update lease optimistically, falling back to slow path", "lock", le.config.Lock.Describe()) + logger.V(2).Info("Failed to update lease optimistically, falling back to slow path", "lock", le.config.Lock.Describe(), "err", err) } // 2. obtain or create the ElectionRecord