You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2016/08/24 09:34:20 UTC

[jira] [Closed] (FLINK-4454) Lookups for JobManager address in config

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

Maximilian Michels closed FLINK-4454.
-------------------------------------
    Resolution: Fixed

master: 720645587bc58a22db6a8d948f91384da2ecb7b7
release-1.1: 70b818b1ba27e5e7d4758c438801681cbf5aee81

> 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)