[
https://issues.apache.org/jira/browse/FLINK-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944825#comment-14944825
]
ASF GitHub Bot commented on FLINK-2805:
---------------------------------------
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/1227#issuecomment-145808965
Exactly. If the blob server dies, then the job manager will still shutdown
the cache service though. This is the same behaviour as in the job manager
recovery. Thinking about it, I am wondering myself what we gain by removing the
shutdown hook. In case of hard failures (or kill -9) the shutdown hook is not
called anyways and for all other cases the job manager will shutdown the
components manually anyways. Am I missing something?
> Make user jars available for all job managers to recover
> --------------------------------------------------------
>
> Key: FLINK-2805
> URL: https://issues.apache.org/jira/browse/FLINK-2805
> Project: Flink
> Issue Type: Bug
> Components: BlobManager, JobManager
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
>
> This is a bug in https://github.com/apache/flink/pull/1153.
> In case of multiple job managers, the user jars need to be accessible by all
> job managers (including those who arrive later).
> Since #1153 requires the file state backend to be configured, the simplest
> solution is to make the blob server aware of the configured recovery mode and
> put/get/delete the user jars from the file state backend as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
