If we submit a job through CLI and it has an error ( missing args and so on ) , the JM goes into convulsions. It seems it submits a job without fist validating and then goes into a loop trying to figure out the job
Jul 06 16:51:26 flink-9edd15d7.bf2.tumblr.net docker[31171]: at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) Jul 06 16:51:26 flink-9edd15d7.bf2.tumblr.net docker[31171]: at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107) Jul 06 16:51:26 flink-9edd15d7.bf2.tumblr.net docker[31171]: Caused by: org.apache.flink.runtime.messages.FlinkJobNotFoundException: Could not find Flink job (0de3cb47d32dd25ba0375d97bfd07387) Jul 06 16:51:26 flink-9edd15d7.bf2.tumblr.net docker[31171]: at org.apache.flink.runtime.dispatcher.Dispatcher.getJobMasterGatewayFuture(Dispatcher.java:693) Jul 06 16:51:26 flink-9edd15d7.bf2.tumblr.net docker[31171]: at org.apache.flink.runtime.dispatcher.Dispatcher.requestJob(Dispatcher.java:459) Jul 06 16:51:26 flink-9edd15d7.bf2.tumblr.net docker[31171]: at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source) Is this known ? |
The UI shows the following and the JM goes into a convulsions trying to retrieve a jobiid as above. org.apache.flink.client.program.ProgramInvocationException: The main method caused an error. On Fri, Jul 6, 2018 at 4:53 PM, Vishal Santoshi <[hidden email]> wrote:
|
It seems it is the UI refresh that forces the loop on the job server. From flink cli it does it once.. So this might be a false alarm. On Fri, Jul 6, 2018 at 4:55 PM, Vishal Santoshi <[hidden email]> wrote:
|
This happens usually if you have an old tab open for a job which has been finished and is not archived. Then you cluster won't find this job anymore. Cheers, Till On Fri, Jul 6, 2018 at 11:11 PM Vishal Santoshi <[hidden email]> wrote:
|
Free forum by Nabble | Edit this page |