[
https://issues.apache.org/jira/browse/FLINK-22995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364108#comment-17364108
]
Till Rohrmann commented on FLINK-22995:
---------------------------------------
Are you sure that you don't have another Flink cluster running using the same
{{kubernetes.cluster-id}} [~bhagi__R]? If this is the case, then both clusters
will use the same config map and only one instance can gain the leadership.
What you need to do is to set a unique {{cluster-id}}.
> Failed to acquire lease 'ConfigMapLock: .... retrying...
> --------------------------------------------------------
>
> Key: FLINK-22995
> URL: https://issues.apache.org/jira/browse/FLINK-22995
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Affects Versions: 1.13.1
> Reporter: Bhagi
> Priority: Blocker
> Attachments: jobamanger.log
>
>
> Hi Team,
> I have deployed Flink session cluster on standalone k8s with Jobmanager HA
> (k8s HA service).
> when i am submitting the jobs all jobs are failed. due to jobmanager leader
> election issue.
> attaching the logs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)