You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Andrey Zagrebin (Jira)" <ji...@apache.org> on 2020/05/15 09:57:00 UTC

[jira] [Closed] (FLINK-17652) Legacy JM heap options should fallback to new JVM_HEAP_MEMORY in standalone

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

Andrey Zagrebin closed FLINK-17652.
-----------------------------------
    Resolution: Fixed

merged into master by 9b3732db57bb76c77222f548f4ea4931dd4237a4

> Legacy JM heap options should fallback to new JVM_HEAP_MEMORY in standalone
> ---------------------------------------------------------------------------
>
>                 Key: FLINK-17652
>                 URL: https://issues.apache.org/jira/browse/FLINK-17652
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Configuration, Runtime / Coordination
>            Reporter: Andrey Zagrebin
>            Assignee: Andrey Zagrebin
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.11.0
>
>
> FLINK-16742 states that the legacy JM heap options should fallback to JobManagerOptions.JVM_HEAP_MEMORY in standalone scripts. BashJavaUtils#getJmResourceParams has been implemented to fallback to JobManagerOptions.TOTAL_FLINK_MEMORY. This should be fixed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)