dannycranmer commented on pull request #18733: URL: https://github.com/apache/flink/pull/18733#issuecomment-1043014193
> Maybe we could solve that by overriding the thread factory from the ELG and setting the context manually (not sure if thats doable)? Possibly. Would we check which classloader the ELG is using and replicate that to the thread context? If we are going to this extent, maybe we could add a `static Map<JobId, ELG>` in the AWS util class and to create a separate ELG per job as discussed (and copy the counting aspects of `SharedSdkEventLoopGroup`). I am not sure how we would acquire the job ID though, are there any context objects we can grab this from? Do you think this edge case is worth the investment now? Since it is non-standard to bundle and load these dependencies from the parent classloader. I am sure there are plenty of edge cases similar to this where static namespace in parent loader cause issues. For example, Kafka Security providers. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
