[
https://issues.apache.org/jira/browse/FLINK-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14951760#comment-14951760
]
ASF GitHub Bot commented on FLINK-2804:
---------------------------------------
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/1249#issuecomment-147070413
+1 good to merge. We have to remove dc9daef before merging though (that was
a temporary work around, because we didn't support blocking HA submissions.
Should I close the other recovery PRs as this one contains all respective
additions?
I've tested it out locally and it works fine. I think moving this to the
job client actor is better than having it the repeated retrieval in the job
client. And the addition with the submission and connection timeouts are also
very good.
> Support blocking job submission with Job Manager recovery
> ---------------------------------------------------------
>
> Key: FLINK-2804
> URL: https://issues.apache.org/jira/browse/FLINK-2804
> Project: Flink
> Issue Type: Improvement
> Affects Versions: 0.10
> Reporter: Ufuk Celebi
> Assignee: Till Rohrmann
> Priority: Minor
>
> Submitting a job in a blocking fashion with JobManager recovery and a failing
> JobManager fails on the client side (the one submitting the job). The job
> still continues to be recovered.
> I propose to add simple support to re-retrieve the leading job manager and
> update the client actor with it and then wait for the result as before.
> As of the current standing in PR #1153
> (https://github.com/apache/flink/pull/1153) the job manager assumes that the
> same actor is running and just keeps on sending execution state updates etc.
> (if the listening behaviour is not detached).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
