with the io.fabric8 K8s client, I am not sure how to handle
> it. Any help and guidance would be much appreciated.
>
> Thanks,
>
> -- Forwarded message -
> From: Berkay Polat
> Date: Thu, Nov 17, 2022 at 12:36 PM
> Subject: Stand alone K8s HA mode with Static To
ld be much appreciated.
Thanks,
-- Forwarded message -
From: Berkay Polat
Date: Thu, Nov 17, 2022 at 12:36 PM
Subject: Stand alone K8s HA mode with Static Tokens Used by Service Accounts
To:
Hi,
Our team has been using flink 1.15 and we have a stand alone K8s flink
setup that
Hi,
Our team has been using flink 1.15 and we have a stand alone K8s flink
setup that uses K8s HA services for its HA mode. Recently, our organization
is in the works of updating their EKS clusters' Kubernetes versions to 1.21
or later. We received a request from our support team that the service
Could you please share the full JobManager logs?
AFAIK, you attached exceptions are normal logs when the JobManager is
trying to acquire the configmap lock.
Best,
Yang
houssem 于2021年8月31日周二 上午4:36写道：
> Hello, thanks for the response
>
> I am using kubernetes standalone application mode not the
Hello, thanks for the response
I am using kubernetes standalone application mode not the native one.
and this error happens randomly at some point while running the job.
Also i am using just one replicas of the jobmanager
here is some other logs::
{"@timestamp":"2021-08-30T15:43:44.970+02:00"
Hello,
Do I understand correctly that you are using native Kubernetes
deployment in application mode;
and the issue *only* happens if you set kubernetes-jobmanager-replicas
[1] to a value greater than 1?
Does it happen during deployment or at some point while running the job?
Could you share Fli
hello i am deploying a flink application cluster with kubernetes HA mode, but i
am facing this recurrent problem and i didn't know how to solve it.
Any help would be appreciated.
this of the jobManager:
{"@timestamp":"2021-08-27T14:19:42.447+02:00","@version":"1","message":"Exception
occurr
