Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14961
Hm, I can't get this test to fail with Netty 4.0.41 when I 'mvn install'
and run the test suite locally. I'm having a hard time seeing what could
alleviate the failure.
I suspect that this change might be relevant:
https://github.com/netty/netty/commit/1a9ea2d349c42f7c7ccb56daea29f083ee60870e#diff-23eafd00fcd66829f8cce343b26c236a
In any event, we ideally want to fix-forward and find a way to work with
the current version, unless we have reason to believe it's an unresolved bug
(and we don't have a pressing bug fix we need to ingest).
I suppose one hacky way to test the theory above is to push a commit here
that sets this in `NettyUtils`:
```
static {
System.setProperty("io.netty.recycler.maxCapacity", "0");
}
```
... or post a change that tries the `UnpooledByteBufAllocator` to see how
that behaves.
It may not be worth it if it's hard to get this working, but, if it's _not_
really a Netty bug but a behavior change, we'll eventually have to sort this
out.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
