Re: JobManager shows TaskManager was lost/killed while TaskManger Process is still running and the network is OK.

>From what I read in [1], simply add JVM options to env.java.opts as you would when you start a Java program yourself, so setting "-XX:+UseG1GC" should enable G1. Nico [1] https://ci.apache.org/projects/flink/flink-docs-release-1.3/setup/ config.html#common-options On Friday, 15 September

Re: JobManager shows TaskManager was lost/killed while TaskManger Process is still running and the network is OK.

HI All, Even I am facing the same issue. My code fails after running for 15 hours throwing same "Task Manager lost/killed exception". Can we please know the possible solution in detail for this? Rahul Raj On 15 September 2017 at 23:06, AndreaKinn wrote: > Hi, sorry for

Re: JobManager shows TaskManager was lost/killed while TaskManger Process is still running and the network is OK.

The zookeeper related logs are loged by user codes,I finally find the reason why the taskmanger was lost,that was I gave the taskmanager a big amount of memory, the jobmanager identify the taskmanager is down during the taskmanager in Full GC.Thanks for your help. -- View this message in

Re: JobManager shows TaskManager was lost/killed while TaskManger Process is still running and the network is OK.

Hi Renkai, it seems to me as if the TM lost its network connection somehow. Therefore, the JM's heartbeat won't get answered and it marks the TM as terminated. This would also explain why the TM can not longer talk to ZooKeeper. Is this problem reproducible? If so, could you share the full logs

Re: JobManager shows TaskManager was lost/killed while TaskManger Process is still running and the network is OK.

some additional logs I found in jobManager. 2016-11-25 07:19:57,958 WARN akka.remote.RemoteWatcher - Detected unreachable: [akka.tcp://flink@10.17.123.56:59247] 2016-11-25 07:19:57,962 INFO org.apache.flink.runtime.jobmanager.JobManager -

JobManager shows TaskManager was lost/killed while TaskManger Process is still running and the network is OK.

I use the newest snapshot of Flink, all jobs failed since a TaskManager was lost/killed.There is a sample of jobmanager and taskmanager logs //job manager java.lang.Exception: TaskManager was lost/killed: ResourceID{resourceId='8f4b98897b1cbdbb576cbf298ac1339f'} @ 10.17.123.56