为什么Flink在运行时采用的是ChildFirstClassLoader？
Hi All, 看了Flink源代码，发现在实际运行的时候采用的是ChildFirstClassLoader，破坏了双亲模式，请问为什么采用这种设计，是有什么考虑吗？*来自志愿者整理的flink邮件归档
写回答
-
The benefit of inverted classloading is that jobs can use different library versions than Flink’s core itself, which is very useful when the different versions of the libraries are not compatible. The mechanism helps to avoid the common dependency conflict errors like IllegalAccessError or NoSuchMethodError. Different parts of the code simply have separate copies of the classes (Flink’s core or one of its dependencies can use a different copy than the user code). In most cases, this works well and no additional configuration from the user is needed
You can find some details at https://ci.apache.org/projects/flink/flink-docs-master/monitoring/debugging_classloading.html, maybe it will help you.*来自志愿者整理的flink
2021-12-07 16:33:30赞同 展开评论 打赏
版权声明：本文内容由阿里云实名注册用户自发贡献，版权归原作者所有，阿里云开发者社区不拥有其著作权，亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容，填写侵权投诉表单进行举报，一经查实，本社区将立刻删除涉嫌侵权内容。
