[
https://issues.apache.org/jira/browse/FLINK-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027462#comment-16027462
]
ASF GitHub Bot commented on FLINK-5476:
---------------------------------------
GitHub user DmytroShkvyra opened a pull request:
https://github.com/apache/flink/pull/4001
[FLINK-5476] Fail fast if trying to submit a job to a non-existing Fl…
Fail fast if trying to submit a job to a non-existing Flink cluster
- [ ] General
- The pull request references the related JIRA issue ("[FLINK-5476] Jira
title text")
- The pull request addresses only one issue
- Each commit in the PR has a meaningful commit message (including the
JIRA id)
- [ ] Documentation
- Documentation has been added for new functionality
- Old documentation affected by the pull request has been updated
- JavaDoc for public methods has been added
- [ ] Tests & Build
- Functionality added by the pull request is covered by tests
- `mvn clean verify` has been executed successfully locally or a Travis
build has passed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/DmytroShkvyra/flink FLINK-5476-1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/4001.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 #4001
----
commit cd3b8e38a1dd6214ff2d6e540a2b9c8454cd38a1
Author: DmytroShkvyra <[email protected]>
Date: 2017-05-27T15:36:32Z
[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
> Assignee: Dmytro Shkvyra
> 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)
