You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/01/06 14:26:00 UTC
[jira] [Resolved] (FLINK-15369) MiniCluster use fixed network /
managed memory sizes by default
[ https://issues.apache.org/jira/browse/FLINK-15369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann resolved FLINK-15369.
-----------------------------------
Resolution: Fixed
Fixed via
master: 229d02147ee4d57deb05c28a5626f44aca7fcba5
1.10.0: bbb9e70ba4f9bf7343739731ddcd7467bd95050c
> MiniCluster use fixed network / managed memory sizes by default
> ---------------------------------------------------------------
>
> Key: FLINK-15369
> URL: https://issues.apache.org/jira/browse/FLINK-15369
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
> Reporter: Xintong Song
> Assignee: Xintong Song
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, Mini Cluster may allocate off-heap memory (managed & network) according to the JVM free heap size and configured off-heap fractions. This could lead to unnecessary large off-heap memory usage and unpredictable / hard-to-understand behaviors.
> We believe a fix value for managed / network memory would be enough for a such a setup that runs Flink as a library.
> Detailed discussion can be found in this [ML thread|http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Some-feedback-after-trying-out-the-new-FLIP-49-memory-configurations-td36129.html].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)