You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Kostas Kloudas (JIRA)" <ji...@apache.org> on 2016/07/12 09:17:20 UTC
[jira] [Created] (FLINK-4199) Wrong client behavior when submitting
job to non-existing cluster
Kostas Kloudas created FLINK-4199:
-------------------------------------
Summary: Wrong client behavior when submitting job to non-existing cluster
Key: FLINK-4199
URL: https://issues.apache.org/jira/browse/FLINK-4199
Project: Flink
Issue Type: Bug
Reporter: Kostas Kloudas
Trying to submit a job jar from the client to a non-existing cluster gives the following messages. In particular the last line: "Job has been submitted with" is totally misleading.
Cluster retrieved: Standalone cluster with JobManager at localhost/127.0.0.1:6123
Using address localhost:6123 to connect to JobManager.
JobManager web interface address http://localhost:8081
Starting execution of program
Submitting job with JobID: 9c7120e5cc55b2a9157a7e2bc5a12c9d. Waiting for job completion.
org.apache.flink.client.program.ProgramInvocationException: The program execution failed: Communication with JobManager failed: Lost connection to the JobManager.
Job has been submitted with JobID 9c7120e5cc55b2a9157a7e2bc5a12c9d
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)