[
https://issues.apache.org/jira/browse/FLINK-14637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Zagrebin updated FLINK-14637:
------------------------------------
Description: At the moment after
[-FLINK-13982-|https://issues.apache.org/jira/browse/FLINK-13982], when we do
not account for adhoc direct memory allocations for Flink framework (except
network buffers) or done by some libraries used in Flink. In general, we expect
this allocations to stay under a certain reasonably low limit but we have to
have some margin for them so that JVM direct memory limit is not exactly equal
to network buffers and does not fail. We can address it by introducing
framework off heap memory config option. (was: At the moment after
[-FLINK-13982-|https://issues.apache.org/jira/browse/FLINK-13982], when we do
not account for adhoc direct memory allocations for Flink framework (except
network buffers) or done by some used libraries used in Flink. In general, we
expect this allocations to stay under a certain reasonably low limit but we
have to have some margin for them so that JVM direct memory limit is not
exactly equal to network buffers and does not fail. We can address it by
introducing framework off heap memory config option.)
> Introduce framework off heap memory config
> ------------------------------------------
>
> Key: FLINK-14637
> URL: https://issues.apache.org/jira/browse/FLINK-14637
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Task
> Reporter: Andrey Zagrebin
> Assignee: Xintong Song
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> At the moment after
> [-FLINK-13982-|https://issues.apache.org/jira/browse/FLINK-13982], when we do
> not account for adhoc direct memory allocations for Flink framework (except
> network buffers) or done by some libraries used in Flink. In general, we
> expect this allocations to stay under a certain reasonably low limit but we
> have to have some margin for them so that JVM direct memory limit is not
> exactly equal to network buffers and does not fail. We can address it by
> introducing framework off heap memory config option.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
