[ec2-fleet] java.util.concurrent.CancellationException

15 views
Skip to first unread message

Alan Sparks

unread,
Jan 8, 2020, 3:16:10 PM1/8/20
to Jenkins Users

I’m using the current (1.17.1) of the ec2-fleet plugin.  I’ve configured the plugin to use an autoscaling group.  It generally works OK, except occasionally for unknown reasons it launches extra builder instances, wasting money.

 

When I see the issue happen, it logs the following to the Jenkins log.  Does anyone know what this exception is telling me, why it would be happening?

 

Thanks in advance for any hints or suggestions.

-Alan

 

 

2020-01-08 19:51:07.553+0000 [id=39]    SEVERE  hudson.slaves.NodeProvisioner#lambda$update$6: Unexpected uncaught exception encountered while processing agent FleetNode-0

java.util.concurrent.CancellationException: Task was cancelled.

        at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:295)

        at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276)

        at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111)

        at hudson.slaves.NodeProvisioner.lambda$update$6(NodeProvisioner.java:236)

        at hudson.model.Queue._withLock(Queue.java:1392)

        at hudson.model.Queue.withLock(Queue.java:1269)

        at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:223)

        at hudson.slaves.NodeProvisioner.access$900(NodeProvisioner.java:63)

        at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:817)

        at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:70)

        at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58)

        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

        at java.lang.Thread.run(Thread.java:748)

2020-01-08 19:51:07.554+0000 [id=39]    INFO    c.a.j.e.NoDelayProvisionStrategy#apply: currentDemand 1 availableCapacity 0 (availableExecutors 0 connectingExecutors 0 plannedCapacitySnapshot 0 additionalPlannedCapacity 0)

 

 

Alan Sparks

unread,
Jan 14, 2020, 1:38:46 PM1/14/20
to Jenkins Users
No one else has seen this issue?  Because of this, we sometimes get an extra VM running, which wastes money...  Thanks for any ideas.
-Alan

Alan Sparks

unread,
Jan 23, 2020, 11:31:06 AM1/23/20
to Jenkins Users
Was able to get answer via GitHub issue: https://github.com/jenkinsci/ec2-fleet-plugin/issues/167
Was a bug in ec2-fleet plugin, fixed in version 1.17.3 of the plugin.
Reply all
Reply to author
Forward
0 new messages