[
https://issues.apache.org/jira/browse/FLINK-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14324364#comment-14324364
]
Robert Metzger edited comment on FLINK-1556 at 2/17/15 4:15 PM:
----------------------------------------------------------------
Also, it seems that these "fail-fast" jobs are not properly removed from the
jobmanager?
http://imgur.com/PyuQEfm
was (Author: rmetzger):
Also, it seems that these "failearily" jobs are not properly removed from the
jobmanager?
http://imgur.com/PyuQEfm
> JobClient does not wait until a job failed completely if submission exception
> -----------------------------------------------------------------------------
>
> Key: FLINK-1556
> URL: https://issues.apache.org/jira/browse/FLINK-1556
> Project: Flink
> Issue Type: Bug
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
>
> If an exception occurs during job submission the {{JobClient}} received a
> {{SubmissionFailure}}. Upon receiving this message, the {{JobClient}}
> terminates itself and returns the error to the {{Client}}. This indicates to
> the user that the job has been completely failed which is not necessarily
> true.
> If the user directly after such a failure submits another job, then it might
> be the case that not all slots of the formerly failed job are returned. This
> can lead to a {{NoRessourceAvailableException}}.
> We can solve this problem by waiting for the completion of the job failure in
> the {{JobClient}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
