[
https://issues.apache.org/jira/browse/FLINK-21143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17272520#comment-17272520
]
Yang Wang commented on FLINK-21143:
-----------------------------------
If you mean the exception happens on the Flink client side, then I think it is
the expected behavior. Because the jars in the provided lib directory are only
used for JobManager and TaskManager.
The mechanism how provided lib works is to skip the unnecessary uploading(lib,
plugins) from local and register remote directory as Yarn public distributed
cache.
> 【runtime】flink job use the lib jars instead of the `yarn.provided.lib.dirs`
> config jars
> ---------------------------------------------------------------------------------------
>
> Key: FLINK-21143
> URL: https://issues.apache.org/jira/browse/FLINK-21143
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN, Runtime / Configuration
> Affects Versions: 1.12.0
> Reporter: zhisheng
> Priority: Major
> Attachments: flink-deploy-sql-client-.log, flink-deploy-sql-client.log
>
>
> Flink 1.12.0, I had use `yarn.provided.lib.dirs` config to speed up the job
> start，so I upload all jars in HDFS，but I update the jars in HDFS（not
> flink-1.12.0/lib/），it will still use the lib/ jars instead of use the new
> HDFS jars when I submit new job.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
