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

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Resolved
• Affects Version/s: 1.2.0, 1.3.0
• Component/s: Command Line Client
• Labels: pull-request-available
• Assignee: Dmytro Shkvyra
• Reporter: Till Rohrmann
• Created: 12/Jan/17 15:33
• Updated: 17/Oct/19 12:41
• Resolved: 24/Apr/17 10:44

Description

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.

Issue Links

• requires: FLINK-5786 Add support GetClusterStatus message for standalong flink cluster
• links to: GitHub Pull Request #3498
• links to: GitHub Pull Request #3753
• links to: GitHub Pull Request #4001
• links to: GitHub Pull Request #4001