[
https://issues.apache.org/jira/browse/FLINK-15836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Wang updated FLINK-15836:
------------------------------
Description:
As the discussion in the PR[1], if the {{watchReconnectLimit}} is configured by
users via java properties or environment, the watch may be stopped and all the
changes will not be processed properly. So we need to start a new pods watcher
in {{KubernetesResourceManager}} when the old one is closed with exception.
[1]. [https://github.com/apache/flink/pull/10965#discussion_r373491974]
was:
As the discussion in the PR[1], if the {{watchReconnectLimit}} is configured by
users via java properties or environment, the watch may be stopped and all the
changes will not be processed properly. So a fatal exception need to be thrown
when the watcher is closed.
[1]. https://github.com/apache/flink/pull/10965#discussion_r373491974
> Throw fatal exception when the watcher in Fabric8FlinkKubeClient is closed
> --------------------------------------------------------------------------
>
> Key: FLINK-15836
> URL: https://issues.apache.org/jira/browse/FLINK-15836
> Project: Flink
> Issue Type: Sub-task
> Components: Deployment / Kubernetes
> Reporter: Yang Wang
> Assignee: Yang Wang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.1, 1.11.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As the discussion in the PR[1], if the {{watchReconnectLimit}} is configured
> by users via java properties or environment, the watch may be stopped and all
> the changes will not be processed properly. So we need to start a new pods
> watcher in {{KubernetesResourceManager}} when the old one is closed with
> exception.
> [1]. [https://github.com/apache/flink/pull/10965#discussion_r373491974]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
