You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
What happened
It didn't take effect,When set kubernetes.jobmanager.replicas = 2(or higher)on cluster config function.
It is stil one replica on kubernetes cluster!
Flink jobmanager High availability does not take effect!
I have tried various configuration methods but none of them work.
It is a bug!
What you expected to happen
I debugged the program and found that the logic of a high-availability parameter is missing.
See KubernetsOperatorGateway.initResource line 147:
Search before asking
What happened
It didn't take effect,When set kubernetes.jobmanager.replicas = 2(or higher)on cluster config function.
It is stil one replica on kubernetes cluster!
Flink jobmanager High availability does not take effect!
I have tried various configuration methods but none of them work.
It is a bug!
What you expected to happen
I debugged the program and found that the logic of a high-availability parameter is missing.
See KubernetsOperatorGateway.initResource line 147:
How to reproduce
ClusterConfig:
Anything else
Flink version:1.19.1
Dinky version:1.1.0
Version
1.1.0
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: