Flink ShutdownHookManager throws Trying to access closed classloader when destroying itself
I'm working on Flink application which has a kinesis consumer and ElasticSearch sink. My flink job works fine, I get the results I want, except at the end of application execution, when
org.apache.hadoop.util
ShutdownHookManager shutdownExecutor method is called I get this error:
I managed to debug it down to shutdown executor trying to retrieve shutdown timeout:
- getShutdownTimeout(conf);
Which uses:
- new Configuration()
default configuration
Exception is thrown on:
- conf.getTimeDuration(...)
When Configuration
class tries to access non existing inner field of FlinkUserCodeClassLoader.
Does anyone know how to configure Flink application to have FlinkUserCodeClassLoader inner field set to anything but null on default Configuration object?
3 Replies
⌛
This post has been reserved for your question.
Hey @Lil Villa! Please useTIP: Narrow down your issue to simple and precise questions to maximize the chance that others will reply in here./close
or theClose Post
button above when you're finished. Please remember to follow the help guidelines. This post will be automatically closed after 300 minutes of inactivity.
💤
Post marked as dormant
This post has been inactive for over 300 minutes, thus, it has been archived. If your question was not answered yet, feel free to re-open this post or create a new one.
💤
Post marked as dormant
This post has been inactive for over 300 minutes, thus, it has been archived. If your question was not answered yet, feel free to re-open this post or create a new one.
💤
Post marked as dormant
This post has been inactive for over 300 minutes, thus, it has been archived. If your question was not answered yet, feel free to re-open this post or create a new one.
Resolved my problem by adding:
To my sink.
I think it forces my job to use System class loader instead of dynamic flink class loader which somewhere and somewhy was being removed when shutdown executor tries to use it for its own shutdown.
Post Closed
This post has been closed by <@249473164248219648>.