No, I am not starting multiple "per-job clusters".
I didn't configure anything regarding the number of slots per TM, so I guess the default value (1 then).
But on the YARN UI I see that the number of "running containers" varies a lot (13 then 1 then 8 then 2 then 27 then 6 etc...)
Here is the full jobmanager log:
This time it took longer to start (10 minutes)
And completed on this line:
2018-08-07 14:31:11,852 INFO org.apache.flink.runtime.executiongraph.ExecutionGraph - Source: Custom Source -> Sink: Unnamed (1/1) (655509c673d8ae19aac195276ad2c3e6) switched from DEPLOYING to RUNNING.
Thanks a lot for your help and your time,
De : Gary Yao <gary@xxxxxxxxxxxxxxxxx>
Envoyé : mardi 7 août 2018 14:15
À : Florian Simond
Cc : vino yang; user@xxxxxxxxxxxxxxxx
Objet : Re: Could not build the program from JAR file.
5 minutes sounds too slow. Are you starting multiple "per-job clusters" at the
same time? How many slots do you configure per TM? After you submit the job,
how many resources do you have left in your YARN cluster?
It might be that you are affected by FLINK-9455 : Flink requests
unnecessary resources from YARN and blocks the execution of other jobs
temporarily. The workaround is to configure only one slot per TM.
If the above does not help, can you attach the full ClusterEntrypoint
On Tue, Aug 7, 2018 at 12:34 PM, Florian Simond <florian.simond@xxxxxxxxxx> wrote: