You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/11/15 03:59:21 UTC

[GitHub] [flink] wangyang0918 commented on issue #10193: [FLINK-13938][yarn] Use pre-uploaded flink binary and Yarn public distributed cache to accelerate flink submission.

wangyang0918 commented on issue #10193: [FLINK-13938][yarn] Use pre-uploaded flink binary and Yarn public distributed cache to accelerate flink submission.
URL: https://github.com/apache/flink/pull/10193#issuecomment-554201838
 
 
   @TisonKun I just want to redeclare that this PR will have two optimizations.
   1. Use pre-uploaded flink jars to avoid uploading in flink client, it will make the submission very fast. So the corresponding directory will be needed.
   2. Register pre-uploaded flink jars as Yarn public cache. This will make the public cache could be shared by different applications and avoid unnecessary downloading.
   
   I suggest to upload a flink binary to hdfs first, and then the two optimizations will both work as expected. 
   
   If you want to support multiple paths, i just want to know how it works? How to find the corresponding local file and avoid uploading?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services