You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/07/12 12:11:00 UTC

[jira] [Commented] (DRILL-8257) Resolve Netty lib conflicts

    [ https://issues.apache.org/jira/browse/DRILL-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17565445#comment-17565445 ] 

ASF GitHub Bot commented on DRILL-8257:
---------------------------------------

jnturton opened a new pull request, #2593:
URL: https://github.com/apache/drill/pull/2593

   # [DRILL-8257](https://issues.apache.org/jira/browse/DRILL-8257): Resolve Netty lib conflicts
   
   ## Description
   
   The following transitive dependencies in Drill 1.20.* conflict with Drill's own, newer Netty dependencies and need to be excluded.
   
   - jars/3rdparty/netty-transport-native-epoll-4.1.45.Final.jar
   - jars/3rdparty/netty-all-4.1.59.Final.jar
   - jars/3rdparty/netty-codec-http-4.1.59.Final.jar
   
   This PR introduces a Netty BOM. Note that Drill in the past picked up a dependency on every Netty component (netty-all) through the OCI HDFS connector:
   
   ```
   [INFO] -

> Resolve Netty lib conflicts
> ---------------------------
>
>                 Key: DRILL-8257
>                 URL: https://issues.apache.org/jira/browse/DRILL-8257
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: library
>    Affects Versions: 1.20.1
>            Reporter: James Turton
>            Assignee: James Turton
>            Priority: Major
>             Fix For: 1.20.2
>
>
> The following transitive dependencies conflict with Drill's own, newer Netty dependencies and need to be excluded.
>  * jars/3rdparty/netty-transport-native-epoll-4.1.45.Final.jar
>  * jars/3rdparty/netty-all-4.1.59.Final.jar
>  * jars/3rdparty/netty-codec-http-4.1.59.Final.jar
> It is not understood what exact conditions are needed for the library conflict to adversely affect a Drillbit, but when they are present it becomes impossible to enable TLS on the user RPC port. One guess is that a class loader race condition decides whether the problem will manifest.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)