[
https://issues.apache.org/jira/browse/FLINK-8673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-8673.
--------------------------------
Resolution: Fixed
Fixed via 075f5b6930b86e110a32e290229b9800be72a3a7
> Don't let JobManagerRunner shut down itself
> -------------------------------------------
>
> Key: FLINK-8673
> URL: https://issues.apache.org/jira/browse/FLINK-8673
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination
> Affects Versions: 1.5.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
> Labels: flip-6
> Fix For: 1.5.0
>
>
> Currently, the {{JobManagerRunner}} is allowed to shut down itself in case of
> a job completion. This, however, can cause problems when the {{Dispatcher}}
> receives a request for a {{JobMaster}}. If the {{Dispatcher}} is not told
> about the shut down of the {{JobMaster}} then it might still try to send
> requests to it. This will lead to time outs.
> It would be better to simply let the {{JobManagerRunner}} not shut down
> itself and defer it to the owner (the {{Dispatcher}}). We can do this by
> listening on the {{JobManagerRunner#resultFuture}} which is completed by the
> {{JobManagerRunner}} in case of a successful job completion or a failure.
> That way we could also get rid of the {{OnCompletionActions}} and the
> {{FatalErrorHandler}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
