[ 
https://issues.apache.org/jira/browse/FLINK-21432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17295732#comment-17295732
 ] 

Yang Wang commented on FLINK-21432:
-----------------------------------

1) 
https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/resource-providers/standalone/kubernetes/#starting-a-kubernetes-cluster-session-mode

2) 
[https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/resource-providers/standalone/kubernetes/#high-availability-with-standalone-kubernetes]

3) For non-HA mode, TaskManager uses K8s service to register to JobManager. And 
for HA mode, the HA service will be used to retrieve the leader address.

 

If you want to start multiple JobManagers, then we do not have a documentation 
now. I am trying to find some time to work on this FLINK-21382. Please follow 
my last comments and change a bit about the args for the session cluster.

> Web UI -- Error - {"errors":["Service temporarily unavailable due to an 
> ongoing leader election. Please refresh."]}
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-21432
>                 URL: https://issues.apache.org/jira/browse/FLINK-21432
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / Kubernetes
>    Affects Versions: 1.12.0
>         Environment: debian
>            Reporter: Bhagi
>            Priority: Critical
>             Fix For: 1.12.0
>
>         Attachments: image-2021-02-22-10-39-06-180.png, 
> image-2021-02-23-23-12-03-118.png, image-2021-02-23-23-14-13-708.png, 
> image-2021-02-23-23-27-38-247.png, image-2021-03-04-14-14-14-471.png, 
> image-2021-03-04-15-20-17-475.png
>
>
> Web UI – throwing this Error 
> {"errors":["Service temporarily unavailable due to an ongoing leader 
> election. Please refresh."]}
> Please find Job Manager logs.
>  
> !image-2021-02-22-10-39-06-180.png!



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

Reply via email to