You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Binh-Nguyen Tran (Jira)" <ji...@apache.org> on 2022/12/28 08:44:00 UTC
[jira] [Created] (FLINK-30518) [flink-operator] Kubernetes HA not working due to wrong jobmanager.rpc.address
Binh-Nguyen Tran created FLINK-30518:
----------------------------------------
Summary: [flink-operator] Kubernetes HA not working due to wrong jobmanager.rpc.address
Key: FLINK-30518
URL: https://issues.apache.org/jira/browse/FLINK-30518
Project: Flink
Issue Type: Bug
Components: Kubernetes Operator
Affects Versions: kubernetes-operator-1.3.0
Environment: ~ flinkdeployment.yaml ~
```
spec:
flinkConfiguration:
high-availability: kubernetes
high-availability.storageDir: "file:///opt/flink/storage"
...
jobManager:
replicas: 3
```
Reporter: Binh-Nguyen Tran
Attachments: flink-configmap.png
Since flink-conf.yaml is mounted as read-only configmap, the /docker-entrypoint.sh script is not able to inject correct Pod IP to `jobmanager.rpc.address`. This leads to same address (e.g flink.ns-ext) being set for all Job Manager pods. This causes:
(1) flink-cluster-config-map always contains same address for all 3 component leaders (see screenshot)
(2) Accessing Web UI when jobmanager.replicas > 1 is not possible with error
```
{"errors":["Service temporarily unavailable due to an ongoing leader election. Please refresh."]}
```
--
This message was sent by Atlassian Jira
(v8.20.10#820010)