[
https://issues.apache.org/jira/browse/FLINK-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Zagrebin closed FLINK-14631.
-----------------------------------
Resolution: Won't Do
After having a longer discussion, the conclusion is that we do not make this
change but account for netty arenas in framework off memory config FLINK-14637.
This should become even less problem after we merge
[FLINK-10742|https://issues.apache.org/jira/browse/FLINK-10742].
> Account for netty direct allocations in direct memory limit (Netty Shuffle)
> ---------------------------------------------------------------------------
>
> Key: FLINK-14631
> URL: https://issues.apache.org/jira/browse/FLINK-14631
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Task
> Reporter: Andrey Zagrebin
> Assignee: Andrey Zagrebin
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> At the moment after FLINK-13982, when we calculate JVM direct memory limit,
> we only account for memory segment network buffers but not for direct
> allocations from netty arenas in
> org.apache.flink.runtime.io.network.netty.NettyBufferPool. We should include
> netty arenas into shuffle memory calculations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
