Closed asizemore closed 1 year ago
This may be related to a misfired attempt to clear the cache. For some reason the postgres instance backing compute was not cleared as expected and now has a bunch of dead job references.
On the backend we are seeing this error:
java.lang.IllegalStateException: Attempted to lookup result files from nonexistent workspace 04fc82883614bcc12a5a8d2d57d21af7
at org.veupathdb.lib.compute.platform.intern.s3.S3.getNonReservedFiles(S3.kt:142) ~[service.jar:1.0.0]
at org.veupathdb.lib.compute.platform.AsyncPlatform.getJobFiles(AsyncPlatform.kt:200) ~[service.jar:1.0.0]
at org.veupathdb.service.eda.compute.EDA.getComputeJobFiles(EDA.kt:189) ~[service.jar:1.0.0]
at org.veupathdb.service.eda.compute.controller.ComputeController.resultFile(ComputeController.java:212) ~[service.jar:1.0.0]
at org.veupathdb.service.eda.compute.controller.ComputeController.postComputesRankedabundanceByFile(ComputeController.java:109) ~[service.jar:1.0.0]
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:577) ~[?:?]
at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory.lambda$static$0(ResourceMethodInvocationHandlerFactory.java:52) ~[service.jar:1.0.0]
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:134) ~[service.jar:1.0.0]
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:177) ~[service.jar:1.0.0]
at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:176) ~[service.jar:1.0.0]
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:81) ~[service.jar:1.0.0]
at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:478) ~[service.jar:1.0.0]
at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:400) ~[service.jar:1.0.0]
at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:81) ~[service.jar:1.0.0]
at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:261) ~[service.jar:1.0.0]
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248) ~[service.jar:1.0.0]
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244) ~[service.jar:1.0.0]
at org.glassfish.jersey.internal.Errors.process(Errors.java:292) ~[service.jar:1.0.0]
at org.glassfish.jersey.internal.Errors.process(Errors.java:274) ~[service.jar:1.0.0]
at org.glassfish.jersey.internal.Errors.process(Errors.java:244) ~[service.jar:1.0.0]
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:265) ~[service.jar:1.0.0]
at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:240) ~[service.jar:1.0.0]
at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:697) ~[service.jar:1.0.0]
at org.glassfish.jersey.grizzly2.httpserver.GrizzlyHttpContainer.service(GrizzlyHttpContainer.java:367) ~[service.jar:1.0.0]
at org.glassfish.grizzly.http.server.HttpHandler$1.run(HttpHandler.java:190) ~[service.jar:1.0.0]
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:535) ~[service.jar:1.0.0]
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:515) ~[service.jar:1.0.0]
at java.lang.Thread.run(Thread.java:833) ~[?:?]
Now on QA:
Success!! Closing ticket!
We get this message on only some pairs of config. Get this error with
But all works fine with
It's not just DailyBaby. Also seen in CAMP
So far i've only seen this error when the compute had already Completed. I haven't yet seen it immediately after I run the compute.