But isn't that a normal stack trace which you see when you submit a job to the cluster via the CLI and somewhere in the compilation process something fails?
Anyway, it would be helpful to see the program which causes this problem. Cheers, Till On Mon, Feb 15, 2016 at 12:25 PM, Fabian Hueske <fhue...@gmail.com> wrote: > Hi, > > This stacktrace looks really suspicious. > It includes classes from the submission client (CLIClient), optimizer > (JobGraphGenerator), and runtime (KryoSerializer). > > Is it possible that you try to start a new Flink job inside another job? > This would not work. > > Best, Fabian >
