Hey,
Is that whole Task Manager log? Have you checked memory issues both on Task
Managers and the Job Manager? Like out of memory/long GC pauses as I suggested
in the first email?
After you rule memory issues, you could capture couple of thread dumps (`kill
-3 JVM_PID` or `jstack JVM_PID`) an
Hello,
this is the task manage log but it does not change after I run the
program. I think the Flink planner has problem with my program. It can
not even start the job.
Best,
Alieh
018-12-10 12:20:20,386 INFO
org.apache.flink.runtime.taskexecu
Hi,
Have you checked task managers logs?
Piotrek
> On 8 Dec 2018, at 12:23, Alieh wrote:
>
> Hello Piotrek,
>
> thank you for your answer. I installed a Flink on a local cluster and used
> the GUI in order to monitor the task managers. It seems the program does not
> start at all. The whole
Hello Piotrek,
thank you for your answer. I installed a Flink on a local cluster and
used the GUI in order to monitor the task managers. It seems the program
*d**oes not start at all*. The whole time just the job manager is
struggling... For very very toy examples, after a long time (during th
Hi,
Please investigate logs/standard output/error from the task manager that has
failed (the logs that you showed are from job manager). Probably there is some
obvious error/exception explaining why has it failed. Most common reasons:
- out of memory
- long GC pause
- seg fault or other error fr
