You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Bhagi (Jira)" <ji...@apache.org> on 2021/03/04 06:42:00 UTC

[jira] [Created] (FLINK-21594) Flink - {"errors":["Service temporarily unavailable due to an ongoing leader election. Please refresh."]}

Bhagi created FLINK-21594:
-----------------------------

             Summary: Flink - {"errors":["Service temporarily unavailable due to an ongoing leader election. Please refresh."]}
                 Key: FLINK-21594
                 URL: https://issues.apache.org/jira/browse/FLINK-21594
             Project: Flink
          Issue Type: Bug
          Components: Deployment / Kubernetes
    Affects Versions: 1.12.0
         Environment: debian kubernetes
            Reporter: Bhagi
             Fix For: 1.12.0
         Attachments: image-2021-03-04-11-59-24-095.png, image-2021-03-04-12-06-12-504.png

Hi Team,

I deployed standalone Flink session cluster on kubernetes.. i have created the HA with 3 job managers. But Flink Web UI is throwing an error saying

"\{"errors":["Service temporarily unavailable due to an ongoing leader election. Please refresh."]}".

Please help to fix the issue with UI and HA.

Logs are showing with the Leader election and updated to the all configmaps..

below configmaps are created in the same namespace where flink cluster is running.

111-dispatcher-leader 
111-resourcemanager-leader 
111-restserver-leader

but i have one doubt on configmap created, when i described above configmaps showing type as flink-native-kubernetes.. But i created cluster with flink standalone kubernetes.

 configmap-type: high-availability
 type: flink-native-kubernetes 

 

2) Let me know how to confirm the whether flink is running on native kubernetes or standalone kubernetes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)