[ https://issues.apache.org/jira/browse/FLINK-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944794#comment-14944794 ]
ASF GitHub Bot commented on FLINK-2805: --------------------------------------- Github user tillrohrmann commented on the pull request: https://github.com/apache/flink/pull/1227#issuecomment-145799064 What happens with the jars on HDFS if the last `BlobServer` dies without properly calling `shutdown`? They will only be removed if a new Flink cluster is started with the same `STATE_BACKEND_FS_RECOVERY_PATH` and shut down properly? > 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)