You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Neelesh Srinivas Salian (JIRA)" <ji...@apache.org> on 2016/08/29 23:59:20 UTC

[jira] [Commented] (FLINK-2247) Improve the way memory is reported in the web frontend

    [ https://issues.apache.org/jira/browse/FLINK-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15447477#comment-15447477 ] 

Neelesh Srinivas Salian commented on FLINK-2247:
------------------------------------------------

Hi [~tvas], please let me know if this is still valid. 

> Improve the way memory is reported in the web frontend
> ------------------------------------------------------
>
>                 Key: FLINK-2247
>                 URL: https://issues.apache.org/jira/browse/FLINK-2247
>             Project: Flink
>          Issue Type: Improvement
>          Components: Webfrontend
>            Reporter: Theodore Vasiloudis
>            Priority: Trivial
>
> Currently in the taskmanager view of the web frontend, the memory available to Flink is reported in a slightly confusing manner.
> In the worker summary, we get a report of the Flink Managed memory available, and we get warnings when that is set too low.
> The warnings though seem to be not taking the memory available to Flink when being issued.
> For example, in a machine with 7.5GB memory available it is normal to assign ~6GB for the JVM, which under default settings gives ~4GB to Flink managed memory.
> In this case however, we get a warning that 7500MB of memory is available, but only ~$4000MB is available to Flink, disregarding the total amount available to the JVM.
> The reporting can then be improved by reporting the total amount available for the JVM, the amount available for Flink's managed memory, and only issue warnings when the settings are actually low compared to the available memory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)