Thanks Lijie/Biao
To put it simply, what we like to achieve is to replace env.runAsync() with
some code that uses application mode.
@Lijie: When I set deployment mode to application I got the following
exception after submitting the job
Caused by: java.lang.IllegalStateException: No ExecutorFact
Hi there,
Currently, YARN Application mode only supports running a jar job. And as
Lijie said, the main method is executed on JM, so if I understand
correctly, your previous way of running execute() method on client side to
submit a job to YARN cluster may not work. A quick workaround is to create
Hi,
I think the difference between ApplicationMode and PerJob is just where the
main method is executed (ApplicationMode executes on JM, PerJob executes on
client side). So I think your original job code should work well under
ApplicationMode. Did you encounter any problems?
You can get more detail
Hi Experts,
We are planning to migrate our flink jobs from per-job mode to application
mode in our platform. Our jobs are basically SQL scripts so we have some
custom Java code to leverage Flink's SQL and Table API to build the
execution environment and execute the jobs on Yarn. We would like to k
