You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhu Zhu (Jira)" <ji...@apache.org> on 2020/01/22 03:57:00 UTC
[jira] [Closed] (FLINK-15632) Zookeeper HA service could not work
for active kubernetes integration
[ https://issues.apache.org/jira/browse/FLINK-15632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhu Zhu closed FLINK-15632.
---------------------------
Resolution: Fixed
Fixed via:
master:
003ceb9a78f90803b2a765e007e4487eead00e06
be4b713c4de8ecd6ba52fe930dfbea6b380416dc
cd9836c43bc615bd8a4475920df607e37cfd89ef
release-1.10:
dbfdfc469c8983682c8bb398e9511b94a45c3cf4
5bc7bdd4efb887ecea03f46b9df316fc6f474216
e1436f8172d61d610d892a3f4e24ab137d3e03b6
> Zookeeper HA service could not work for active kubernetes integration
> ---------------------------------------------------------------------
>
> Key: FLINK-15632
> URL: https://issues.apache.org/jira/browse/FLINK-15632
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Reporter: Yang Wang
> Assignee: Yang Wang
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It will be some different, if we want to support HA for active Kubernetes integration.
> # The K8s service is designed for accessing the jobmanager out of K8s cluster. So Flink client will not use HA service to retrieve address of jobmanager. Instead, it always use Kubernetes service to contact with jobmanager via rest client.
> # The Kubernetes DNS creates A and SRV records only for Services. It doesn't generate pods' A records. So the ip address, not hostname, will be used as jobmanager address.
>
> All other behaviors will be same as Zookeeper HA for standalone and Yarn.
> To fix this problem, we just need some minor changes to {{KubernetesClusterDescriptor}} and {{KubernetesSessionEntrypoint}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)