You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ruguo Yu (Jira)" <ji...@apache.org> on 2020/12/20 04:56:00 UTC
[jira] [Updated] (FLINK-20681) Support specifying the hdfs path
when ship archives or files
[ https://issues.apache.org/jira/browse/FLINK-20681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruguo Yu updated FLINK-20681:
-----------------------------
Description:
Currently, our team try to submit flink job that depends extra resource with yarn-application target, and use two options: "yarn.ship-archives" and "yarn.ship-files".
But above options only support specifying local resource and shiping them to hdfs, besides if it can support remote resource on distributed filesystem (such as hdfs), then get the following benefits：
* client will exclude the local resource uploading to accelerate the job submission process
* yarn will cache them on the nodes so that they doesn't need to be downloaded for application
was:
Currently, our team try to submit flink job that depends extra resource with yarn-application target, and use two options: "yarn.ship-archives" and "yarn.ship-files".
But above options only support specifying local resource and shiping them to hdfs, besides if it can support remote resource on distributed filesystem (such as hdfs), then get the following benefits：
* client will exclude the local resource uploading to accelerate the job submission process
* yarn will cache them on the nodes so that they doesn't need to be downloaded every time for each application
> Support specifying the hdfs path when ship archives or files
> -------------------------------------------------------------
>
> Key: FLINK-20681
> URL: https://issues.apache.org/jira/browse/FLINK-20681
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Affects Versions: 1.12.0
> Reporter: Ruguo Yu
> Priority: Major
> Labels: pull-requests-available
> Fix For: 1.13.0
>
>
> Currently, our team try to submit flink job that depends extra resource with yarn-application target, and use two options: "yarn.ship-archives" and "yarn.ship-files".
> But above options only support specifying local resource and shiping them to hdfs, besides if it can support remote resource on distributed filesystem (such as hdfs), then get the following benefits：
> * client will exclude the local resource uploading to accelerate the job submission process
> * yarn will cache them on the nodes so that they doesn't need to be downloaded for application
--
This message was sent by Atlassian Jira
(v8.3.4#803005)