[jira] [Closed] (FLINK-6629) ClusterClient cannot submit jobs to HA cluster if address not set in configuration

["Till Rohrmann (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann closed FLINK-6629.
--------------------------------
    Resolution: Fixed

1.4.0: d246515963e6f736dc78114ae1dbecbbcd93ed32
1.3.0: f783e529c558ac3df68b4e69fb931f2d55b55db7

> ClusterClient cannot submit jobs to HA cluster if address not set in configuration
> ----------------------------------------------------------------------------------
>
>                 Key: FLINK-6629
>                 URL: https://issues.apache.org/jira/browse/FLINK-6629
>             Project: Flink
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 1.3.0, 1.2.1, 1.4.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Blocker
>             Fix For: 1.3.0, 1.4.0
>
>
> In the general case, the {{ClusterClient}} fails to submit jobs to an HA cluster. The problem is the {{LazyActorSystemLoader}} which creates an {{ActorSystem}}, upon first call. The {{ActorSystem}} is created by reading the JobManager's address from the {{Configuration}} in order to find the connecting address via {{ConnectionUtils.findConnectingAddress}}. The address in the configuration is, however, only valid in the non-HA case. In the HA case, we have to obtain the leader's address from ZooKeeper. Therefore, if  the address is not explicitly set in the {{flink-conf.yaml}}, then the {{ClusterClient}} might either fail with a {{RuntimeException}} if no address at all has been specified or it will use an invalid address and retrieve the wrong connecting address.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)