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

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2017/01/12 15:33:52 UTC

[jira] [Created] (FLINK-5476) Fail fast if trying to submit a job to a non-existing Flink cluster

Till Rohrmann created FLINK-5476:
------------------------------------

             Summary: Fail fast if trying to submit a job to a non-existing Flink cluster
                 Key: FLINK-5476
                 URL: https://issues.apache.org/jira/browse/FLINK-5476
             Project: Flink
          Issue Type: Improvement
          Components: Client
    Affects Versions: 1.2.0, 1.3.0
            Reporter: Till Rohrmann
            Priority: Minor


In case of entering the wrong job manager address when submitting a job via {{flink run}}, the {{JobClientActor}} waits per default {{60 s}} until a {{JobClientActorConnectionException}}, indicating that the {{JobManager}} is no longer reachable, is thrown. In order to fail fast in case of wrong connection information, we could change it such that it uses initially a much lower timeout and only increases the timeout if it had at least once successfully connected to a {{JobManager}} before.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)