[
https://issues.apache.org/jira/browse/FLINK-17707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-17707:
-----------------------------------
Labels: pull-request-available stale-assigned (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 14, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it. If the "warning_label" label is not removed in 7 days, the
issue will be automatically unassigned.
> Support configuring replica of Deployment based HA setups
> ---------------------------------------------------------
>
> Key: FLINK-17707
> URL: https://issues.apache.org/jira/browse/FLINK-17707
> Project: Flink
> Issue Type: New Feature
> Components: Deployment / Kubernetes, Runtime / Coordination
> Reporter: Canbin Zheng
> Assignee: Yang Wang
> Priority: Major
> Labels: pull-request-available, stale-assigned
>
> At the moment, in the native K8s setups, we hard code the replica of
> Deployment to 1. However, when users enable the ZooKeeper
> HighAvailabilityServices, they would like to configure the replica of
> Deployment also for faster failover.
> This ticket proposes to make *replica* of Deployment configurable in the
> ZooKeeper based HA setups.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
