From 0058d0e264e6d04152046116a3cc09e31fb7fc8f Mon Sep 17 00:00:00 2001 From: Craig Silverstein Date: Wed, 23 Jul 2014 14:19:00 -0700 Subject: [PATCH] More logging when we decide to time out a slave. Summary: They're timing out much more often than I'd expect -- even when we're doing back-to-back deploys they are timing out. Not sure why. I am hoping this logging will shed some light. Test Plan: Fingers crossed. Reviewers: chris Reviewed By: chris Differential Revision: http://phabricator.khanacademy.org/D11464 --- src/main/java/hudson/plugins/ec2/EC2RetentionStrategy.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/java/hudson/plugins/ec2/EC2RetentionStrategy.java b/src/main/java/hudson/plugins/ec2/EC2RetentionStrategy.java index e1bddcf92..25a5a865b 100644 --- a/src/main/java/hudson/plugins/ec2/EC2RetentionStrategy.java +++ b/src/main/java/hudson/plugins/ec2/EC2RetentionStrategy.java @@ -69,7 +69,7 @@ public synchronized long check(EC2Computer c) { // TODO: really think about the right strategy here final long idleMilliseconds = System.currentTimeMillis() - c.getIdleStartMilliseconds(); if (idleMilliseconds > TimeUnit2.MINUTES.toMillis(idleTerminationMinutes)) { - LOGGER.info("Idle timeout: "+c.getName()); + LOGGER.info("Idle timeout: " + c.getName() + " after " + idleTerminationMinutes + " minutes (idle since time_t " + (int)(c.getIdleStartMilliseconds() / 1000) + ")"); c.getNode().idleTimeout(); } }