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

ASF GitHub Bot updated FLINK-5476:
----------------------------------
    Labels: pull-request-available  (was: )

> 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: Command Line Client
>    Affects Versions: 1.2.0, 1.3.0
>            Reporter: Till Rohrmann
>            Assignee: Dmytro Shkvyra
>            Priority: Minor
>              Labels: pull-request-available
>
> 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
(v8.3.4#803005)

Reply via email to