You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/09/02 12:00:46 UTC
[jira] [Commented] (FLINK-2472) Make the JobClientActor check
periodically if the submitted Job is still running and if the JobManager is
still alive
[ https://issues.apache.org/jira/browse/FLINK-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727110#comment-14727110 ]
ASF GitHub Bot commented on FLINK-2472:
---------------------------------------
Github user sachingoel0101 commented on the pull request:
https://github.com/apache/flink/pull/979#issuecomment-137010239
This most likely requires a re-work because of the latest changes in Job Manager and Client. Closing for now while I re-examine all the logic. Will reopen it in a few days.
> Make the JobClientActor check periodically if the submitted Job is still running and if the JobManager is still alive
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-2472
> URL: https://issues.apache.org/jira/browse/FLINK-2472
> Project: Flink
> Issue Type: Improvement
> Reporter: Till Rohrmann
> Assignee: Sachin Goel
>
> In case that the {{JobManager}} dies without notifying possibly connected {{JobClientActors}} or if the job execution finishes without sending the {{SerializedJobExecutionResult}} back to the {{JobClientActor}}, it might happen that a {{JobClient.submitJobAndWait}} never returns.
> I propose to let the {{JobClientActor}} periodically check whether the {{JobManager}} is still alive and whether the submitted job is still running. If not, then the {{JobClientActor}} should return an exception to complete the waiting future.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)