[ https://issues.apache.org/jira/browse/FLINK-18742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17183685#comment-17183685 ]
Matt Wang commented on FLINK-18742: ----------------------------------- [~rmetzger] The `CoreOptions.CHECK_LEAKED_CLASSLOADER` is introduced by this PR( [https://github.com/apache/flink/pull/13027). |https://github.com/apache/flink/pull/13027] It can work after removing this line `[https://github.com/apache/flink/commit/d9af11d372cc76efefed50f544f67c45223b8bb5#diff-da45a35dae282e565a61be1441256883L148]` [|https://github.com/apache/flink/pull/13027] > Some configuration args do not take effect at client > ---------------------------------------------------- > > Key: FLINK-18742 > URL: https://issues.apache.org/jira/browse/FLINK-18742 > Project: Flink > Issue Type: Improvement > Components: Command Line Client > Affects Versions: 1.11.1 > Reporter: Matt Wang > Assignee: Matt Wang > Priority: Major > Labels: pull-request-available > Fix For: 1.12.0 > > > Some configuration args from command line will not work at client, for > example, the job sets the {color:#505f79}_classloader.resolve-order_{color} > to _{color:#505f79}parent-first,{color}_ it can work at TaskManager, but > Client doesn't. > The *FlinkUserCodeClassLoaders* will be created before calling the method of > _{color:#505f79}getEffectiveConfiguration(){color}_ at > {color:#505f79}org.apache.flink.client.cli.CliFrontend{color}, so the > _{color:#505f79}Configuration{color}_ used by > _{color:#505f79}PackagedProgram{color}_ does not include Configuration args. -- This message was sent by Atlassian Jira (v8.3.4#803005)