You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user-zh@flink.apache.org by "kellygeorge13@163.com" <ke...@163.com> on 2024/03/12 03:36:49 UTC
回复：flink operator 高可用任务偶发性报错unable to update ConfigMapLock
有没有高手指点一二？？？在线等
---- 回复的原邮件 ----
| 发件人 | kellygeorge13@163.com |
| 日期 | 2024年03月11日 20:29 |
| 收件人 | user-zh<us...@flink.apache.org> |
| 抄送至 | |
| 主题 | flink operator 高可用任务偶发性报错unable to update ConfigMapLock |
jobmanager的报错如下所示，请问是什么原因？
Exception occurred while renewing lock:Unable to update ConfigMapLock
Caused by:io.fabric8.kubernetes.client.Kubernetes Client Exception:Operation:[replace] for kind:[ConfigMap] with name:[flink task xxxxxx- configmap] in namespace:[default]
Caused by: Java.net.SocketTimeoutException:timeout
Re: flink operator 高可用任务偶发性报错unable to update ConfigMapLock
Posted by Yang Wang <wa...@apache.org>.
这种一般是因为APIServer那边有问题导致单次的ConfigMap renew lease annotation的操作失败，Flink默认会重试的
如果你发现因为这个SocketTimeoutException原因导致了任务Failover，可以把下面两个参数调大
high-availability.kubernetes.leader-election.lease-duration: 60s
high-availability.kubernetes.leader-election.renew-deadline: 60s
Best,
Yang
On Tue, Mar 12, 2024 at 11:38 AM kellygeorge13@163.com <
kellygeorge13@163.com> wrote:
> 有没有高手指点一二？？？在线等
>
>
>
> ---- 回复的原邮件 ----
> | 发件人 | kellygeorge13@163.com |
> | 日期 | 2024年03月11日 20:29 |
> | 收件人 | user-zh<us...@flink.apache.org> |
> | 抄送至 | |
> | 主题 | flink operator 高可用任务偶发性报错unable to update ConfigMapLock |
> jobmanager的报错如下所示，请问是什么原因？
> Exception occurred while renewing lock:Unable to update ConfigMapLock
>
> Caused by:io.fabric8.kubernetes.client.Kubernetes Client
> Exception:Operation:[replace] for kind:[ConfigMap] with name:[flink task
> xxxxxx- configmap] in namespace:[default]
>
>
> Caused by: Java.net.SocketTimeoutException:timeout
>
>
>
>
>
>
>