You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (JIRA)" <ji...@apache.org> on 2019/01/10 12:08:00 UTC
[jira] [Closed] (FLINK-11272) Support for parsing multiple
--yarnship parameters
[ https://issues.apache.org/jira/browse/FLINK-11272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aljoscha Krettek closed FLINK-11272.
------------------------------------
Resolution: Fixed
Merged on master in
f692d372f7cb1ecd04ad82d9d546fe68c702ce05
> Support for parsing multiple --yarnship parameters
> --------------------------------------------------
>
> Key: FLINK-11272
> URL: https://issues.apache.org/jira/browse/FLINK-11272
> Project: Flink
> Issue Type: Improvement
> Components: Job-Submission, YARN
> Affects Versions: 1.7.1
> Reporter: leesf
> Assignee: leesf
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When using flink run -m yarn-cluster ** command to submit application to yarn, flink only supports parsing one --yarnship parameter now, which might not be suitable for the following scenarios: Application submitted to yarn depends on jars which are divided into common jars and application-specific jars, the common jars are the same to all applications while application-specific jars are different according to different applications. The current processing way in flink is to put all jars in one directory and specify the directory with --yarnship. There is no problem when submit job in sequence (put application-specific jar and common jars into one directory dynamicly), but it is not so efficient. It can be improved by parsing multiple --yarnship parameters that place the application-specific jars in a different directory from other common jars, then we can submit job concurrently.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)