[
https://issues.apache.org/jira/browse/FLINK-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433129#comment-15433129
]
ASF GitHub Bot commented on FLINK-4454:
---------------------------------------
GitHub user mxm opened a pull request:
https://github.com/apache/flink/pull/2406
[FLINK-4454] always retrieve JobManager address using LeaderRetrievalService
CC @uce This should solve the reported problems on the mailing if an
invalid JobManager address has been set in the config but HA mode is enabled.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mxm/flink FLINK-4454
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2406.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2406
----
commit 86acb89c1557787a92c1d3fdf5e5755d87ed0fbf
Author: Maximilian Michels <[email protected]>
Date: 2016-08-23T16:11:45Z
[FLINK-4454] always retrieve JobManager address using LeaderRetrievalService
----
> Lookups for JobManager address in config
> ----------------------------------------
>
> Key: FLINK-4454
> URL: https://issues.apache.org/jira/browse/FLINK-4454
> Project: Flink
> Issue Type: Bug
> Components: Client
> Affects Versions: 1.2.0, 1.1.1
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Minor
> Fix For: 1.2.0, 1.1.2
>
>
> At a few non-critical places for printing status messages, the code in
> ClusterClient checks for the JobManager address in the config. All these
> calls have to be replaced with a leader retrieval to make sure the correct
> information is printed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
