[
https://issues.apache.org/jira/browse/FLINK-26216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494981#comment-17494981
]
Biao Geng commented on FLINK-26216:
-----------------------------------
hi [~ConradJam] thanks a lot for your words but I do not have the permission to
assign this ticket. Before we ask help from others, I just want to mention that
in the [Jira|https://issues.apache.org/jira/browse/FLINK-26163?filter=-1] of
refactor FlinkUtils, I have added codes like:
{quote}effectiveConfig.setInteger(KubernetesConfigOptions.KUBERNETES_JOBMANAGER_REPLICAS,
spec.getJobManager().getReplicas());
{quote}
And I verified it on my own k8s cluster and 2 JM can be started correctly.
Please let me konw if that is your expected fix. If that is true, maybe we do
not need to do it twice(sorry for the late update in this jira). If that is not
your case, I believe we can ask others to assign this ticket to you.
> Make 'replicas' work in JobManager Spec
> ---------------------------------------
>
> Key: FLINK-26216
> URL: https://issues.apache.org/jira/browse/FLINK-26216
> Project: Flink
> Issue Type: Sub-task
> Components: Kubernetes Operator
> Reporter: Biao Geng
> Priority: Minor
>
> In our flink kubernetes operator's cr, we allow users to set the replica of
> JobManager.
> But in our {{FlinkUtils#getEffectiveConfig}} method, we currently not set
> this value from the yaml file and as a result, the {{replicas}} will not work
> and the default value(i.e. 1) will be applied.
> Though we believe one JM with KubernetesHaService should be enough for most
> HA cases, the {{replicas}} field of JM also makes sense since more than one
> JM can reduce down time and make recovery of JM failure faster.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
