Hi, Gary I think it might be a bug. So would you like to open a jira for this. And could you share the exception ,which the TaskManagerLocation is null? It might be very helpful to verify the cause.
Best, Guowei On Thu, May 13, 2021 at 10:36 AM Yangze Guo <karma...@gmail.com> wrote: > Hi, it seems to be related to FLINK-22276. Thus, I'd involve Matthias > to take a look. > > @Matthias My gut feeling is that not all execution who has failureInfo > has been deployed? > > Best, > Yangze Guo > > On Wed, May 12, 2021 at 10:12 PM Gary Wu <gary...@appier.com> wrote: > > > > Hi, > > > > We have upgraded our Flink applications to 1.13.0 but we found that Root > Exception can not be shown on Web UI with an internal server error message. > After opening browser development console and trace the message, we found > that there is a exception in jobmanager: > > > > 2021-05-12 13:30:45,589 ERROR > org.apache.flink.runtime.rest.handler.job.JobExceptionsHandler [] - > Unhandled exception. > > java.lang.IllegalArgumentException: The location must not be null for a > non-global failure. > > at > org.apache.flink.util.Preconditions.checkArgument(Preconditions.java:138) > ~[flink-dist_2.12-1.13.0.jar:1.13.0] > > at > org.apache.flink.runtime.rest.handler.job.JobExceptionsHandler.assertLocalExceptionInfo(JobExceptionsHandler.java:218) > ~[flink-dist_2.12-1.13.0.jar:1.13.0] > > at > org.apache.flink.runtime.rest.handler.job.JobExceptionsHandler.createRootExceptionInfo(JobExceptionsHandler.java:191) > ~[flink-dist_2.12-1.13.0.jar:1.13.0] > > at > java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195) > ~[?:?] > > at java.util.stream.SliceOps$1$1.accept(SliceOps.java:199) ~[?:?] > > at > java.util.ArrayList$ArrayListSpliterator.tryAdvance(ArrayList.java:1632) > ~[?:?] > > at > java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:127) > ~[?:?] > > at > java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:502) > ~[?:?] > > at > java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:488) ~[?:?] > > at > java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474) > ~[?:?] > > at > java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913) > ~[?:?] > > at > java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:?] > > at > java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578) > ~[?:?] > > at > org.apache.flink.runtime.rest.handler.job.JobExceptionsHandler.createJobExceptionHistory(JobExceptionsHandler.java:169) > ~[flink-dist_2.12-1.13.0.jar:1.13.0] > > at > org.apache.flink.runtime.rest.handler.job.JobExceptionsHandler.createJobExceptionsInfo(JobExceptionsHandler.java:154) > ~[flink-dist_2.12-1.13.0.jar:1.13.0] > > at > org.apache.flink.runtime.rest.handler.job.JobExceptionsHandler.handleRequest(JobExceptionsHandler.java:101) > ~[flink-dist_2.12-1.13.0.jar:1.13.0] > > at > org.apache.flink.runtime.rest.handler.job.JobExceptionsHandler.handleRequest(JobExceptionsHandler.java:63) > ~[flink-dist_2.12-1.13.0.jar:1.13.0] > > at > org.apache.flink.runtime.rest.handler.job.AbstractExecutionGraphHandler.lambda$handleRequest$0(AbstractExecutionGraphHandler.java:87) > ~[flink-dist_2.12-1.13.0.jar:1.13.0] > > at > java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:642) > [?:?] > > at > java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478) > [?:?] > > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > [?:?] > > at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?] > > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) > [?:?] > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > [?:?] > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > [?:?] > > at java.lang.Thread.run(Thread.java:834) [?:?] > > > > We would like to check Is there any configuration change should be done > for the application? Thanks! > > > > Regards, > > -Gary > > > > > > > > APPIER EMAIL NOTICE > > > > The contents of this email message and any attachments from Appier Group > Inc. and/or its affiliates may be privileged and confidential. If you are > not the intended recipient of this email, please note that any disclosure, > copying, distribution, or use of this message or its attachments is > prohibited. If you have received this email in error, please contact us > immediately and delete this message and any attachments. >
