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
wrote:
> It seems it is the UI refresh that forces the loop on the job server.
> Fr
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
wrote:
> The UI shows the following and the JM goes into a convulsions trying to
> retrieve a jobiid as above.
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
wrote:
> If we submit a job through CLI and it has an
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.fo
