flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chesnay Schepler (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-2247) Improve the way memory is reported in the web frontend
Date Thu, 13 Oct 2016 19:19:20 GMT

     [ https://issues.apache.org/jira/browse/FLINK-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Chesnay Schepler closed FLINK-2247.
    Resolution: Invalid

We no longer show such warnings in the WebFrontend. We are also showing the amount of managed
memory and total JVM memory.

> 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

View raw message