So I am using the commiunity version of SQ and ran a project through Jenkins that built successfully. I am now getting this project on SQ stuck in the “in progress” for over 2 days now. It is causing other projects to be stuck in pending and from the ce.log below, is the info I get.
Only seems to take this long for this project, where as others it doesnt. Which I do not understand why.
Any help to solve this would be appreciated!
INFO ce[AW2NfvUpi8WieuX9QxEe][o.s.c.t.CeWorkerImpl] Execute task | project=gvpptest | type=REPORT | id=AW2NfvUpi8WieuX9QxEe
2019.10.02 16:54:49 INFO ce[][o.e.c.t.TransportClientNodesService] failed to get node info for {#transport#-1}{mDcPupCTQ6WmgqdHqyQVrQ}{127.0.0.1}{127.0.0.1:9001}, disconnecting...
org.elasticsearch.transport.ReceiveTimeoutTransportException: [][127.0.0.1:9001][cluster:monitor/nodes/liveness] request_id [15123] timed out after [5588ms]
at org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:951)
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:569)
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)
2019.10.02 16:55:01 WARN ce[][o.e.t.TransportService] Received response for a request that has timed out, sent [24794ms] ago, timed out [19206ms] ago, action [cluster:monitor/nodes/liveness], node [{#transport#-1}{mDcPupCTQ6WmgqdHqyQVrQ}{127.0.0.1}{127.0.0.1:9001}], id [15123]