[
https://issues.apache.org/jira/browse/FLINK-14633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Zagrebin updated FLINK-14633:
------------------------------------
Description: At the moment after
[-FLINK-13982-|https://issues.apache.org/jira/browse/FLINK-13982], when we
calculate JVM direct memory limit, we do not account for direct allocations
from netty arenas in org.apache.flink.queryablestate.network.NettyBufferPool.
Alternatively, we account for this in framework off heap memory config
(FLINK-14637). (was: At the moment after
[-FLINK-13982-|https://issues.apache.org/jira/browse/FLINK-13982], when we
calculate JVM direct memory limit, we do not account for direct allocations
from netty arenas in org.apache.flink.queryablestate.network.NettyBufferPool.
Alternatively, we account for this memory in framework off heal memory config
(FLINK-14637).)
> Account for netty direct allocations in direct memory limit (Queryable state)
> -----------------------------------------------------------------------------
>
> Key: FLINK-14633
> URL: https://issues.apache.org/jira/browse/FLINK-14633
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Queryable State, Runtime / Task
> Reporter: Andrey Zagrebin
> Priority: Major
> Fix For: 1.10.0
>
>
> At the moment after
> [-FLINK-13982-|https://issues.apache.org/jira/browse/FLINK-13982], when we
> calculate JVM direct memory limit, we do not account for direct allocations
> from netty arenas in org.apache.flink.queryablestate.network.NettyBufferPool.
> Alternatively, we account for this in framework off heap memory config
> (FLINK-14637).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
