[ 
https://issues.apache.org/jira/browse/FLINK-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15885755#comment-15885755
 ] 

ASF GitHub Bot commented on FLINK-5815:
---------------------------------------

Github user tillrohrmann commented on a diff in the pull request:

    https://github.com/apache/flink/pull/3388#discussion_r103200589
  
    --- Diff: 
flink-yarn/src/main/java/org/apache/flink/yarn/cli/FlinkYarnCLI.java ---
    @@ -85,6 +89,10 @@ public FlinkYarnCLI(String shortPrefix, String 
longPrefix) {
                DETACHED = new Option(shortPrefix + "a", longPrefix + 
"attached", false, "Start attached");
                ZOOKEEPER_NAMESPACE = new Option(shortPrefix + "z", longPrefix 
+ "zookeeperNamespace", true, "Namespace to create the Zookeeper sub-paths for 
high availability mode");
     
    +           LIB_JARS = new Option(shortPrefix + "libjars", longPrefix + 
"libjars", true, "Jar file paths for job, like /home/user/lib/test.jar");
    +           FILES = new Option(shortPrefix + "files", longPrefix + "files", 
true, "Normal file paths for job, like /home/user/lib/test.dict");
    +           ARCHIVES = new Option(shortPrefix + "archives", longPrefix + 
"archives", true, "Archived file uris for job, like 
hdfs:///users/flink/common_dict#dict");
    --- End diff --
    
    I'm wondering whether we shouldn't offer these options also for the 
standalone and mesos case. We could use the BlobStore to distribute the files.


> 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)

Reply via email to