Re: Application cluster - Job execution and cluster creation timeouts

; Request ID: null; Proxy: null)\n\t at org.apache.hadoop.fs.s3a.S3AUtils.translateException(S3AUtils.java:177)\n\t at org.apache.hadoop.fs.s3a.Invoker.once(Invoker.java:111)\n\t at org.apache.hadoop.fs.s3a.Invoker.lambda$retry$3(Invoker.java:260)\n\t at org.apache.hadoop.fs.s3a.Invoker.retryUn

Re: Application cluster - Job execution and cluster creation timeouts

sday, April 7, 2021 6:24 AM To: Tamir Sagi Cc: user@flink.apache.org Subject: Re: Application cluster - Job execution and cluster creation timeouts EXTERNAL EMAIL Hi Tamir, Maybe I did not make myself clear. Here the "deployer" means our internal Flink application deployer(actuall

Re: Application cluster - Job execution and cluster creation timeouts

t > externally.(which makes it more complex) > We could also pull the job status using Flink client, but it become > useless if the job is executed infinite. > > What do you think? > > Best, > Tamir. > > > ------------------ > *From:* Yang Wang >

Re: Application cluster - Job execution and cluster creation timeouts

088647&e=145530340&v=5500b7f1f0cbfd289d5f3053790ae0e36932941ce59f5ce3694a2ae0a6341dcd] From: Yang Wang Sent: Tuesday, April 6, 2021 10:36 AM To: Tamir Sagi Cc: user@flink.apache.org Subject: Re: Application cluster - Job execution and cluster creation timeouts EXTERNAL EMAIL Hi T

Re: Application cluster - Job execution and cluster creation timeouts

Hi Tamir, Thanks for trying the native K8s integration. 1. We do not have a timeout for creating the Flink application cluster. The reason is that the job submission happens on the JobManager side. So the Flink client does not need to wait for the JobManager running and then exit. I think even t

Application cluster - Job execution and cluster creation timeouts

Hey all, We deploy application cluster natively on Kubernetes. are there any timeouts for Job execution and cluster creation? I went over the configuration page here but did not find anything relevant. In order to