[
https://issues.apache.org/jira/browse/TEZ-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor updated TEZ-4157:
------------------------------
Description:
-In the dependency tree, there are 2 occurrences of compile scope direct netty
dependencies, however, they're not used at all. I compiled locally successfully
without them. E.g. when investigating blackduck alerts (complaining about netty
deps for current 3.10.5.Final), it would be cleaner to start from a dependency
tree where Tez doesn't depend on netty directly in order to eliminate its
responsibility (and move the focus to underlying hadoop for instance).-
Tez depends on netty3 almost only in ShuffleHandler and some related classes.
We can eliminate netty3 by upgrading it, but this effort might involve some
testing due to fundamental [changes from
netty3->netty4|https://netty.io/wiki/new-and-noteworthy-in-4.0.html] + we don't
have a reference yet, as [hadoop's
ShuffleHandler|https://github.com/apache/hadoop/blob/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/main/java/org/apache/hadoop/mapred/ShuffleHandler.java]
is still on netty3.
As per the netty documentation, we can also expect some performance improvement
(e.g. Pooled buffers).
was:
-In the dependency tree, there are 2 occurrences of compile scope direct netty
dependencies, however, they're not used at all. I compiled locally successfully
without them.
E.g. when investigating blackduck alerts (complaining about netty deps for
current 3.10.5.Final), it would be cleaner to start from a dependency tree
where Tez doesn't depend on netty directly in order to eliminate its
responsibility (and move the focus to underlying hadoop for instance).-
Tez depends on netty3 almost only in ShuffleHandler and some related classes.
We can eliminate netty3 by upgrading it, but this effort might involve some
testing due to fundamental [changes from
netty3->netty4|https://netty.io/wiki/new-and-noteworthy-in-4.0.html] + we don't
have a reference yet, as [hadoop's
ShuffleHandler|https://github.com/apache/hadoop/blob/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/main/java/org/apache/hadoop/mapred/ShuffleHandler.java]
is still on netty3.
As per the netty documentation, we can also expect some performance improvement
(e.g. Pooled buffers).
> ShuffleHandler: upgrade to netty4
> ---------------------------------
>
> Key: TEZ-4157
> URL: https://issues.apache.org/jira/browse/TEZ-4157
> Project: Apache Tez
> Issue Type: Bug
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
> Attachments: TEZ-4157.01.patch
>
>
> -In the dependency tree, there are 2 occurrences of compile scope direct
> netty dependencies, however, they're not used at all. I compiled locally
> successfully without them. E.g. when investigating blackduck alerts
> (complaining about netty deps for current 3.10.5.Final), it would be cleaner
> to start from a dependency tree where Tez doesn't depend on netty directly in
> order to eliminate its responsibility (and move the focus to underlying
> hadoop for instance).-
> Tez depends on netty3 almost only in ShuffleHandler and some related classes.
> We can eliminate netty3 by upgrading it, but this effort might involve some
> testing due to fundamental [changes from
> netty3->netty4|https://netty.io/wiki/new-and-noteworthy-in-4.0.html] + we
> don't have a reference yet, as [hadoop's
> ShuffleHandler|https://github.com/apache/hadoop/blob/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/main/java/org/apache/hadoop/mapred/ShuffleHandler.java]
> is still on netty3.
> As per the netty documentation, we can also expect some performance
> improvement (e.g. Pooled buffers).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
