You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Kostas Kloudas (Jira)" <ji...@apache.org> on 2020/05/18 16:40:00 UTC
[jira] [Closed] (FLINK-17796) Application mode should respect user
specified classpath configuration
[ https://issues.apache.org/jira/browse/FLINK-17796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kostas Kloudas closed FLINK-17796.
----------------------------------
Resolution: Fixed
Merged on master with b591f906685ee1379d791d296bd0b305cc7e9bb7
and on release-1.11 with 59a657094194d2b1f290037c9404f12ee080566a
> Application mode should respect user specified classpath configuration
> ----------------------------------------------------------------------
>
> Key: FLINK-17796
> URL: https://issues.apache.org/jira/browse/FLINK-17796
> Project: Flink
> Issue Type: Sub-task
> Components: Client / Job Submission
> Affects Versions: 1.11.0
> Reporter: Yang Wang
> Assignee: Yang Wang
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.11.0
>
>
> Currently, when we deploy a Flink application cluster(e.g. Yarn, K8s), {{-C/--classpath}} could not work properly. Since we override the {{PipelineOptions.CLASSPATHS}} in {{YarnApplicationClusterEntrypoint}} and {{KubernetesApplicationClusterEntrypoint}} . Then client updated configuration will not take effect.
> {code:java}
> // code placeholder
> ./bin/flink run-application -p 5 -t yarn-application\
> --classpath file:///flink/shared/dependency.jar ... \
> -Dtaskmanager.memory.process.size=4096m \ examples/streaming/StateMachineExample.jar
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)