[
https://issues.apache.org/jira/browse/FLINK-24682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17440335#comment-17440335
]
Biao Geng commented on FLINK-24682:
-----------------------------------
Hi, [~trohrmann] [~xtsong], would you mind leaving any comments on this issue?
Thanks
> Unify the -C option behavior in both yarn application and per-job mode
> ----------------------------------------------------------------------
>
> Key: FLINK-24682
> URL: https://issues.apache.org/jira/browse/FLINK-24682
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Affects Versions: 1.12.3
> Environment: flink 1.12.3
> yarn 2.8.5
> Reporter: Biao Geng
> Priority: Major
>
> Recently, when switching the job submission mode from per-job mode to
> application mode on yarn, we found the behavior of '-C' ('–-classpath') is
> somehow misleading:
> In per-job mode, the `main()` method of the program is executed in the local
> machine and '-C' option works well when we use it to specify some local user
> jars like -C file://xxxxxx.jar.
> But in application mode, this option works differently: as the `main()`
> method will be executed on the job manager in the cluster, it is unclear
> where the url like `file://xxxxxx.jar` points. It seems that
> `file://xxxxxx.jar` is located on the job manager machine in the cluster due
> to the code. If that is true, it may mislead users as in per-job mode, it
> refers to the the jars in the client machine.
> In summary, if we can unify the -C option behavior in both yarn application
> and per-job mode, it would help users to switch to application mode more
> smoothly and more importantly, it makes it much easier to specify some local
> jars, that should be loaded by UserClassLoader, on the client machine.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
