Hello,
We are deploying a flink application cluster in kubernetes, 2 pods one for
the JM and the other for the TM.
The problem is when we launch load tests we see that task manager memory
usage increases, after the tests are finished and flink stop processing
data the memory usage never comes d
Hello,
Can someone explain to me what is the point of using HA when deploying an
application cluster with a single JM and the checkpoints are not activated.
AFAK when the pod of the JM goes down kubernetes will restart it anyway so
we don't need to activate the HA in this case.
Maybe there's som
Hello,
Does anyone know when the 1.16.0 version will be released please?
Regards.
écrit :
> Hi!
> You should check out the Flink Kubernetes Operator. I think that covers
> all your needs .
>
> https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/
>
> Cheers,
> Gyula
>
> On Sat, 3 Sep 2022 at 13:45, marco andreas
> wrote:
>
&
We are deploying a flink application cluster on k8S. Following the official
documentation the JM is deployed As a job resource , however we are
deploying a long running flink job that is not supposed to be terminated
and also we need to update the image of the flink job.
The problem is that the j
Hello,
Does anyone have the same issue or have an idea why the jobmanager fails to
renew its leadership when using kubernetes ha service.
Configuration :
kubernetes.namespace: flink-ps-flink-dev
high-availability.kubernetes.leader-election.lease-duration: 200 s
high-availability.kubernetes.leader
Hello everyone,
I am deploying a flink application cluster using k8S HA .
I notice this message in the log
@timestamp":"2022-03-21T17:11:39.436+01:00","@version":"1","message":"Renew
deadline reached after 200 seconds while renewing lock ConfigMapLock:
flink-pushavoo-flink-rec -
elifibre-000
Hello flink community,
I am deploying a flink application cluster using a helm chart , the problem
is that the jobmanager component type is a "Job" , and with helm i can't do
an upgrade of the chart in order to change the application image version
because helm is unable to upgrade the docker image