Retaining uploaded job jars on Flink HA restarts on Kubernetes

Hi, I have a very basic Flink HA setup on Kubernetes and wanted to retain job jars on JobManager Restarts. For HA I am using a Zookeeper and a NFS drive mounted on all pods (JobManager and TaskManagers), that is being used for checkpoints and have also set the `web.upload.dir:

strange behavior with jobmanager.rpc.address on standalone HA cluster

Two things: 1. It would be beneficial I think to drop a line somewhere in the docs (probably on the production ready checklist as well as the HA page) explaining that enabling zookeeper "highavailability" allows for your jobs to restart automatically after a

Re: Cannot submit jobs on a HA Standalone JobManager

Hi Julio, I agree that the job submission should work in HA mode if you manually specify the JobManager. At the minimum a proper error message should be shown. Feel free to open an issue in JIRA. You already stated that you can maintain multiple configuration directories as a workaround. It is

Re: How to set fix JobId for my application.

Hi, If I understand correctly, you are using Queryable State to access state of one job from another one. To avoid redeployment, some operator in application B would need to regularly poll the REST API to discover changes of the job id of application A. It is doable but not advised to use

Re: This server is not the leader for that topic-partition

FlinkKafka011Producer uses Kafka 0.11.0.2. However I’m not sure if bumping KafkaProducer version solves this issue or upgrading Kafka. What Kafka version are you using? Piotrek > On 4 May 2018, at 17:55, Alexander Smirnov > wrote: > > Thanks for quick