[
https://issues.apache.org/jira/browse/FLINK-22959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17361518#comment-17361518
]
Till Rohrmann commented on FLINK-22959:
---------------------------------------
Thanks for reporting this issue [~luke123]. It is indeed a known issue that the
uploaded files won't be persisted across restarts of the JobManager process.
The only option is to configure a persistent storage for {{web.upload.dir}}
which is accessible by all JobManager processes. At the moment you would have
to add an S3 implementation of the {{java.nio.file.FileSystem}} to your
classpath and make it discoverable for the SPI because the respective REST
endpoint uses {{java.nio.file.Path}}.
> Keep the job jar files on JobManager
> --------------------------------------
>
> Key: FLINK-22959
> URL: https://issues.apache.org/jira/browse/FLINK-22959
> Project: Flink
> Issue Type: Improvement
> Components: API / Core, Deployment / Kubernetes
> Affects Versions: 1.13.0, 1.13.1
> Environment: flink 1.30
> k8s 1.16.9
> docker image flink:1.13.0
> Reporter: lukehua
> Priority: Major
> Fix For: 1.13.2
>
>
> When i use the flink web ui ,i upload the jar files to the Jobmanager, but i
> can not keep those files when i restart the Jobmanager。This useage happened
> in some scene ，for example upgrade the version of flink cluster or recreate
> the flink cluster i don't need upload the jar files once again , mutilple
> flink clusters enjoy them togeter so i can submit one job on different
> version flink cluster to test the job etc.
> In another way. the flink config "web.upload.dir" can support s3 or hdfs file
> system ,it also satisfied my requirements yet.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
