[
https://issues.apache.org/jira/browse/FLINK-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891925#comment-15891925
]
ASF GitHub Bot commented on FLINK-5815:
---------------------------------------
Github user wenlong88 commented on the issue:
https://github.com/apache/flink/pull/3388
@tillrohrmann sorry for late response, I have addressed the comments.
Thinks for the review.
Currently for standalone, and mesos, there are already some ways to do
things like that, `--classpath `, `DistributedCache in batch` , we need to do
some refactor and make all of this more clear to user in the future before
adding a new one. But it is necessary to make flip-6 implementation in yarn run
well.
the test is not added because the `flink-yarn-test` is disabled, and I was
not able to enable it. Is there any problem in running yarn test now?
> Add resource files configuration for Yarn Mode
> ----------------------------------------------
>
> Key: FLINK-5815
> URL: https://issues.apache.org/jira/browse/FLINK-5815
> Project: Flink
> Issue Type: Improvement
> Components: Client, YARN
> Affects Versions: 1.3.0
> Reporter: Wenlong Lyu
> Assignee: Wenlong Lyu
>
> Currently in flink, when we want to setup a resource file to distributed
> cache, we need to make the file accessible remotely by a url, which is often
> difficult to maintain a service like that. What's more, when we want do add
> some extra jar files to job classpath, we need to copy the jar files to blob
> server when submitting the jobgraph. In yarn, especially in flip-6, the blob
> server is not running yet when we try to start a flink job.
> Yarn has a efficient distributed cache implementation for application running
> on it, what's more we can be easily share the files stored in hdfs in
> different application by distributed cache without extra IO operations.
> I suggest to introduce -yfiles, -ylibjars -yarchives options to FlinkYarnCLI
> to enable yarn user setup their job resource files by yarn distributed cache.
> The options is compatible with what is used in mapreduce, which make it easy
> to use for yarn user who generally has experience on using mapreduce.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)