[
https://issues.apache.org/jira/browse/FLINK-17231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515218#comment-17515218
]
Yang Wang commented on FLINK-17231:
-----------------------------------
We never know when the LoadBalancer will be prepared by cloud provision or
manually. I suggest to throw an exception or at least a warning log to let the
user know Flink client could not connect to JM because of LoadBalancer is not
ready.
> Deprecate possible implicit fallback from LB to NodePort When retrieving
> Endpoint of LB Service
> -----------------------------------------------------------------------------------------------
>
> Key: FLINK-17231
> URL: https://issues.apache.org/jira/browse/FLINK-17231
> Project: Flink
> Issue Type: Sub-task
> Components: Deployment / Kubernetes
> Affects Versions: 1.10.0, 1.10.1
> Reporter: Canbin Zheng
> Assignee: liuzhuo
> Priority: Major
> Labels: auto-unassigned
>
> Currently, if people use the LB Service, when it comes to retrieving the
> Endpoint for the external Service, we make an implicit fallback immediately
> to return the NodePort address and port if we fail to get the LB address in a
> single try. This kind of toleration can confuse the users since the NodePort
> address/port may be unaccessible due to some reasons like network security
> policy, and the users may not know what really happen behind.
> This ticket proposes to always return the LB address/port otherwise throw an
> Exception indicating that the LB is unready or abnormal.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
