[
https://issues.apache.org/jira/browse/FLINK-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15979121#comment-15979121
]
ASF GitHub Bot commented on FLINK-5476:
---------------------------------------
GitHub user DmytroShkvyra opened a pull request:
https://github.com/apache/flink/pull/3753
[FLINK-5476] Fail fast if trying to submit a job to a non-existing Fl…
…ink cluster
Thanks for contributing to Apache Flink. Before you open your pull request,
please take the following check list into consideration.
If your changes take all of the items into account, feel free to open your
pull request. For more information and/or questions please refer to the [How To
Contribute guide](http://flink.apache.org/how-to-contribute.html).
In addition to going through the list, please provide a meaningful
description of your changes.
- [ ] General
- The pull request references the related JIRA issue ("[FLINK-5476] Fail
fast if trying to submit a job to a non-existing Flink cluster")
- [ ] Documentation
- [ ] Tests & Build
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/DmytroShkvyra/flink FLINK-5476
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3753.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 #3753
----
commit e6ca9d1fd2308a0be3e92e4fe59b0a3e98d3bf3d
Author: DmytroShkvyra <[email protected]>
Date: 2017-04-21T17:44:21Z
[FLINK-5476] Fail fast if trying to submit a job to a non-existing Flink
cluster
----
> 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.15#6346)
