As it turns out, Drill makes clever use of the internal details of the Netty memory allocator. But, that code changed significantly in the last couple of years. When I attempted to upgrade, I found that the private features of Netty that the Drill allocator uses no longer exist in the latest Netty.
So, someone will need to understand what that part of the Drill allocator does and design an alternative integration. The particular issue seems to be that Netty had a per-thread allocation cache which seems to not exist in the latest version. - Paul > On May 15, 2017, at 3:58 PM, Sudheesh Katkam <[email protected]> wrote: > > Hi all, > > As part of working on DRILL-5431 [1], I found a bug in Netty [2], which is > due to be fixed in 4.0.48 [3]. Drill is currently using 4.0.27 [4]. Does > anyone foresee issues with upgrading to the latest version of Netty? I > noticed Apache Arrow upgraded to 4.0.41 [5]. > > Thank you, > Sudheesh > > [1] https://issues.apache.org/jira/browse/DRILL-5431 > [2] https://github.com/netty/netty/issues/6709 > [3] https://github.com/netty/netty/pull/6713 > [4] https://github.com/apache/drill/blob/master/pom.xml#L550 > [5] > https://github.com/apache/arrow/commit/3487c2f0cdc2297a80ba3525c192745313b3da48
