Project: Flink (App Definition and Development / Streaming & Messaging)
File: mem_migration.md

title: "Migration Guide" weight: 7 type: docs aliases: /deployment/memory/mem_migration.html /ops/memory/mem_migration.html <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> The memory setup has changed a lot with the 1.10 release for and with the 1.11 release for . Many configuration options were removed or their semantics changed. This guide will help you to migrate the TaskManager memory configuration from Flink to >= 1.10 and the JobManager memory configuration from Flink <= 1.10 to >= 1.11. {{< hint warning >}} It is important to review this guide because the legacy and new memory configuration can result in different sizes of memory components. If you try to reuse your Flink configuration from older versions before 1.10 for TaskManagers or before 1.11 for JobManagers, it can result in changes to the behavior, performance or even configuration failures of your application. {{< /hint >}} <span class="label label-info">Note</span> Before version 1.10 for TaskManagers and before 1.11 for JobManagers, Flink did not require that memory related options are set at all as they all had default values. The requires that at least one subset of the following options is configured explicitly, otherwise the configuration will fail: | &nbsp;&nbsp;for TaskManager:&nbsp;&nbsp; | &nbsp;&nbsp;for JobManager:&nbsp;&nbsp; | | : | :-- | | | | | | | | <br/> and | | <br/> The shipped with Flink sets (since 1.10) and (since 1.11) to make the default memory configuration consistent. This can also help to evaluate and compare the results of the legacy and new memory computations. This chapter shortly lists all changes to Flink's memory configuration options introduced with the 1.10 release. It also references other chapters for more details about migrating to the new configuration options. The following options are completely removed. If they are still used, they will be ignored. <table class="table table-bordered"> <thead> <tr> <th class="text-left">Removed option</th> <th class="text-left">Note</th> </tr> </thead> <tbody> <tr> <td><h5>taskmanager.memory.fraction</h5></td> <td> Check the description of the new option <a href="{{< ref "docs/deployment/config" >}}#taskmanager-memory-managed-fraction">taskmanager.memory.managed.fraction</a>. The new option has different semantics and the value of the deprecated option usually has to be adjusted. See also <a href="#managed-memory">how to migrate managed memory</a>. </td> </tr> <tr> <td><h5>taskmanager.memory.off-heap</h5></td> <td>On-heap <i>managed memory</i> is no longer supported. See also <a href="#managed-memory">how to migrate managed memory</a>.</td> </tr> <tr> <td><h5>taskmanager.memory.preallocate</h5></td> <td>Pre-allocation is no longer supported and <i>managed memory</i> is always allocated lazily. See also <a href="#managed-memory">how to migrate managed memory</a>.</td> </tr> </tbody> </table> The following options are deprecated but if they are still used they will be interpreted as new options for backwards compatibility: <table class="table table-bordered"> <thead> <tr> <th class="text-left">Deprecated option</th> <th class="text-left">Interpreted as</th> </tr> </thead> <tbody> <tr> <td><h5>taskmanager.heap.size</h5></td> <td> <ul> <li><a href="{{< ref

>}}#taskmanager-memory-flink-size">taskmanager.memory.flink.size</a> for <a href="{{< ref "docs/deployment/resource-providers/standalone/overview" >}}">standalone deployment</a></li> <li><a href="{{< ref "docs/deployment/config" >}}#taskmanager-memory-process-size">taskmanager.memory.process.size</a> for containerized deployments</li> </ul> See also <a href="#total-memory-previously-heap-memory">how to migrate total memory</a>. </td> </tr> <tr> <td><h5>taskmanager.memory.size</h5></td> <td><a href="{{< ref "docs/deployment/config" >}}#taskmanager-memory-managed-size">taskmanager.memory.managed.size</a>, see also <a href="#managed-memory">how to migrate managed memory</a>.</td> </tr> <tr> <td><h5>taskmanager.network.memory.min</h5></td> <td><a href="{{< ref "docs/deployment/config" >}}#taskmanager-memory-network-min">taskmanager.memory.network.min</a></td> </tr> <tr> <td><h5>taskmanager.network.memory.max</h5></td> <td><a href="{{< ref "docs/deployment/config" >}}#taskmanager-memory-network-max">taskmanager.memory.network.max</a></td> </tr> <tr> <td><h5>taskmanager.network.memory.fraction</h5></td> <td><a href="{{< ref "docs/deployment/config" >}}#taskmanager-memory-network-fraction">taskmanager.memory.network.fraction</a></td> </tr> </tbody> </table> Although, the network memory configuration has not changed too much it is recommended to verify its configuration. It can change if other memory components have new sizes, e.g. the total memory which the network can be a fraction of. See also . The container cut-off configuration options, `containerized.heap-cutoff-ratio` and `containerized.heap-cutoff-min`, have no effect anymore for TaskManagers. See also . The previous options which were responsible for the total memory used by Flink are `taskmanager.heap.size` or `taskmanager.heap.mb`. Despite their naming, they included not only JVM Heap but also other off-heap memory components. The options have been deprecated. If you use the mentioned legacy options without specifying the corresponding new options, they will be directly translated into the following new options: Total Flink memory () for standalone deployments Total process memory () for containerized deployments (Yarn) It is also recommended using these new options instead of the legacy ones as they might be completely removed in the following releases. See also . JVM Heap memory previously consisted of the managed memory (if configured to be on-heap) and the rest which included any other usages of heap memory. This rest was the remaining part of the total memory, see also . Now, if only total Flink memory or total process memory is configured, then the JVM Heap is the rest of what is left after subtracting all other components from the total memory, see also . Additionally, you can now have more direct control over the JVM Heap assigned to the operator tasks (), see also . The JVM Heap memory is also used by the heap state backends ( or ) if it is chosen for streaming jobs. A part of the JVM Heap is now always reserved for the Flink framework (). See also . See also . The previous option to configure managed memory size (`taskmanager.memory.size`) was renamed to and deprecated. It is recommended to use the new option because the legacy one can be removed in future releases. If not set explicitly, the managed memory could be previously specified as a fraction (`taskmanager.memory.fraction`) of the total memory minus network memory and container cut-off (only for deployments). This option has been completely removed and will have no effect if still used. Please, use the new option instead. This new option will set the to the specified fraction of the if its size is not set explicitly by . If the is chosen for a streaming job, its native memory consumption should now be accounted for in . The RocksDB memory allocation is limited by the size. This should prevent the killing of containers on . You can disable the RocksDB memory control by setting to `false`. See also . Additionally, the following changes have been made: The is always off-heap now. The configuration option `taskmanager.memory.off-heap` is removed and will have no effect

The now uses native memory which is not direct memory. It means that the managed memory is no longer accounted for in the JVM direct memory limit. The is always lazily allocated now. The configuration option `taskmanager.memory.preallocate` is removed and will have no effect anymore. Previously, there were options responsible for setting the JVM Heap size of the JobManager: `jobmanager.heap.size` `jobmanager.heap.mb` Despite their naming, they represented the JVM Heap only for . For the containerized deployments ( and ), they also included other off-heap memory consumption. The size of JVM Heap was additionally reduced by the container cut-off which has been completely removed after 1.11. The mentioned legacy options have been deprecated. If they are used without specifying the corresponding new options, they will be directly translated into the following new options: JVM Heap () for deployments Total process memory () for containerized deployments ( and ) It is also recommended using these new options instead of the legacy ones as they might be completely removed in the following releases. Now, if only the total Flink memory or total process memory is configured, then the is also derived as the rest of what is left after subtracting all other components from the total memory, see also . Additionally, you can now have more direct control over the by adjusting the option. Since 1.10 release, Flink sets the JVM Metaspace and JVM Direct Memory limits for the TaskManager process by adding the corresponding JVM arguments. Since 1.11 release, Flink also sets the JVM Metaspace limit for the JobManager process. You can enable the JVM Direct Memory limit for JobManager process if you set the option. See also . Flink sets the mentioned JVM memory limits to simplify debugging of the corresponding memory leaks and avoid . See also the troubleshooting guide for details about the and OutOfMemoryErrors. For containerized deployments, you could previously specify a cut-off memory. This memory could accommodate for unaccounted memory allocations. Dependencies which were not directly controlled by Flink were the main source of those allocations, e.g. RocksDB, JVM internals, etc. This is no longer available, and the related configuration options (`containerized.heap-cutoff-ratio` and `containerized.heap-cutoff-min`) will have no effect anymore. The new memory model introduced more specific memory components to address these concerns. In streaming jobs which use , the RocksDB native memory consumption should be accounted for as a part of the now. The RocksDB memory allocation is also limited by the configured size of the . See also and . The other direct or native off-heap memory consumers can now be addressed by the following new configuration options: Task off-heap memory () Framework off-heap memory () JVM metaspace () The direct or native off-heap memory consumers can now be addressed by the following new configuration options: Off-heap memory () JVM metaspace () This section describes the changes of the default shipped with Flink. The total memory for TaskManagers (`taskmanager.heap.size`) is replaced by in the default . The value increased from 1024MB to 1728MB. The total memory for JobManagers (`jobmanager.heap.size`) is replaced by in the default . The value increased from 1024MB to 1600MB. See also . {{< hint warning >}} Warning: If you use the new default it can result in different sizes of memory components and can lead to performance changes. {{< /hint >}}