[
https://issues.apache.org/jira/browse/FLINK-22509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17335212#comment-17335212
]
Konstantin Knauf commented on FLINK-22509:
------------------------------------------
If there is a different, documented way to achieve this, I'd be in favor of
deprecating this as soon as possible and not to fix this anymore. [~fly_in_gis]
what do you think?
If there is another RC for Flink 1.13, we might even be able to deprecate this
already in Flink 1.13.
> ./bin/flink run -m yarn-cluster -d submission leads to IllegalStateException
> ----------------------------------------------------------------------------
>
> Key: FLINK-22509
> URL: https://issues.apache.org/jira/browse/FLINK-22509
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN
> Affects Versions: 1.13.0, 1.14.0
> Reporter: Robert Metzger
> Priority: Major
>
> Submitting a detached, per-job YARN cluster in Flink (like this:
> {{./bin/flink run -m yarn-cluster -d
> ./examples/streaming/TopSpeedWindowing.jar}}), leads to the following
> exception:
> {code}
> 2021-04-28 11:39:00,786 INFO org.apache.flink.yarn.YarnClusterDescriptor
> [] - Found Web Interface
> ip-172-31-27-232.eu-central-1.compute.internal:45689 of application
> 'application_1619607372651_0005'.
> Job has been submitted with JobID 5543e81db9c2de78b646088891f23bfc
> Exception in thread "Thread-4" java.lang.IllegalStateException: Trying to
> access closed classloader. Please check if you store classloaders directly or
> indirectly in static fields. If the stacktrace suggests that the leak occurs
> in a third party library and cannot be fixed immediately, you can disable
> this check with the configuration 'classloader.check-leaked-classloader'.
> at
> org.apache.flink.runtime.execution.librarycache.FlinkUserCodeClassLoaders$SafetyNetWrapperClassLoader.ensureInner(FlinkUserCodeClassLoaders.java:164)
> at
> org.apache.flink.runtime.execution.librarycache.FlinkUserCodeClassLoaders$SafetyNetWrapperClassLoader.getResource(FlinkUserCodeClassLoaders.java:183)
> at
> org.apache.hadoop.conf.Configuration.getResource(Configuration.java:2570)
> at
> org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2783)
> at
> org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2758)
> at
> org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2638)
> at org.apache.hadoop.conf.Configuration.get(Configuration.java:1100)
> at
> org.apache.hadoop.conf.Configuration.getTimeDuration(Configuration.java:1707)
> at
> org.apache.hadoop.conf.Configuration.getTimeDuration(Configuration.java:1688)
> at
> org.apache.hadoop.util.ShutdownHookManager.getShutdownTimeout(ShutdownHookManager.java:183)
> at
> org.apache.hadoop.util.ShutdownHookManager.shutdownExecutor(ShutdownHookManager.java:145)
> at
> org.apache.hadoop.util.ShutdownHookManager.access$300(ShutdownHookManager.java:65)
> at
> org.apache.hadoop.util.ShutdownHookManager$1.run(ShutdownHookManager.java:102)
> {code}
> The job is still running as expected.
> Detached submission with {{./bin/flink run-application -t yarn-application
> -d}} works as expected. This is also the documented approach.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
