You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2016/07/18 12:14:20 UTC

[jira] [Assigned] (FLINK-4199) Wrong client behavior when submitting job to non-existing cluster

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

Maximilian Michels reassigned FLINK-4199:
-----------------------------------------

    Assignee: Maximilian Michels

> 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
>          Components: Client
>            Reporter: Kostas Kloudas
>            Assignee: Maximilian Michels
>
> Trying to submit a job jar from the client to a non-existing cluster gives the following messages. In particular the first and last lines: "Cluster retrieved: Standalone cluster with JobManager at localhost/127.0.0.1:6123" and "Job has been submitted with" are totally misleading.
> {code}
> 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
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)