Re: JobManager did not respond within 60000 ms

2018-10-10 Thread Piotr Nowojski
; in one). > > Thanks again Piotrek ! > > Julien. > > - Mail original - > De: "Piotr Nowojski" > À: jpreis...@free.fr > Cc: user@flink.apache.org > Envoyé: Mardi 9 Octobre 2018 10:37:58 > Objet: Re: JobManager did not respond within 6 ms >

Re: JobManager did not respond within 60000 ms

2018-10-09 Thread jpreisner
r Cc: user@flink.apache.org Envoyé: Mardi 9 Octobre 2018 10:37:58 Objet: Re: JobManager did not respond within 6 ms Hi, You have quite complicated job graph and very low memory settings for the job manager and task manager. It might be that long GC pauses are causing this problem. Secondly, there

Re: JobManager did not respond within 60000 ms

2018-10-09 Thread Piotr Nowojski
ond+within+60000+ms&rlz=1C5CHFA_enDE749DE749&oq=flink+JobManager+did+not+respond+within+6+ms&aqs=chrome..69i57.1113j0j7&sourceid=chrome&ie=UTF-8> of this error that points toward high-availability issues. Have you read those previously reported problems? Thanks, Piotrek

JobManager did not respond within 60000 ms

2018-10-09 Thread jpreisner
: JobManager did not respond within 6 ms at org.apache.flink.client.program.ClusterClient.runDetached(ClusterClient.java:524) at org.apache.flink.client.program.StandaloneClusterClient.submitJob(StandaloneClusterClient.java:103) at