, October 18, 2019 6:42 AM
To: Martin, Nick J [US] (IS)
Cc: Ravi Bhushan Ratnakar ; user
Subject: Re: EXT :Re: Jar Uploads in High Availability (Flink 1.7.2)
Hi Martin,
Flink's web UI based job submission is not well suited to be run behind a load
balancer at the moment. The problem is that th
to:ravibhushanratna...@gmail.com]
>> *Sent:* Tuesday, October 15, 2019 10:35 PM
>> *To:* Martin, Nick J [US] (IS)
>> *Cc:* user
>> *Subject:* EXT :Re: Jar Uploads in High Availability (Flink 1.7.2)
>>
>>
>>
>> Hi,
>>
>>
>>
>
ibhushanratna...@gmail.com]
> *Sent:* Tuesday, October 15, 2019 10:35 PM
> *To:* Martin, Nick J [US] (IS)
> *Cc:* user
> *Subject:* EXT :Re: Jar Uploads in High Availability (Flink 1.7.2)
>
>
>
> Hi,
>
>
>
> i was also experiencing with the similar behavior. I
From: Ravi Bhushan Ratnakar [mailto:ravibhushanratna...@gmail.com]
Sent: Tuesday, October 15, 2019 10:35 PM
To: Martin, Nick J [US] (IS)
Cc: user
Subject: EXT :Re: Jar Uploads in High Availability (Flink 1.7.2)
Hi,
i was also experiencing with the similar behavior. I adopted following approach
Hi,
i was also experiencing with the similar behavior. I adopted following
approach
- used a distributed file system(in my case aws efs) and set the
attribute "web.upload.dir", this way both the job manager have same
location.
- on the load balancer side(aws elb), i used "readiness p
I'm seeing that when I upload a jar through the rest API, it looks like only
the Jobmanager that received the upload request is aware of the newly uploaded
jar. That worked fine for me in older versions where all clients were
redirected to connect to the leader, but now that each Jobmanager acce
