Hi Folks,

I'm running Beam Python on Flink on Kubernetes. One thing I'm noticing is
that it takes a really long time for jobs to start. It looks like this
slowdown is due to the cost of uploading the Flink Beam Uber Jar (~225 Mb)
to the Job server.

Is there any way to speed this up?

1. Can the JAR be cached in the Flink job manager and Flink task manager to
be reused across runs?
2. Is it possible to bake the JAR into my docker images and avoid uploading
it on each run?
3. Should I run a dedicated beam job server separate from the flink cluster?

Thanks
J

Reply via email to