【Flink】Direct buffer memory taskmanager.memory.task.off-heap.size

九师兄

已于 2022-04-18 18:48:30 修改

阅读量1.8k

点赞数

分类专栏：大数据-flink 文章标签： flink Direct buffer memory

于 2021-06-04 19:37:19 首次发布

本文为博主九师兄（QQ:541711153 欢迎来探讨技术）原创文章，未经允许博主不允许转载。

本文链接：https://blog.csdn.net/qq_21383435/article/details/117569723

版权

大数据-flink 专栏收录该内容

854 篇文章 860 订阅 ¥99.90 ¥299.90

订阅专栏

本文探讨了Flink中Direct buffer memory引发的内存问题。当遇到直接内存溢出错误时，可能是作业需要增大JVM直接内存或存在内存泄漏。通过调整'taskmanager.memory.task.off-heap.size'和'taskmanager.memory.framework.off-heap.size'配置可解决部分问题。此外，还提到了Maven安装插件问题和如何手动引入依赖。

摘要由CSDN通过智能技术生成

文章目录

1.场景1
- 1.1 概述
2.场景2

1.场景1

1.1 概述

Direct buffer memory. The direct out-of-memory error has occurred. This can mean two things: either job(s) require(s) a larger size of JVM direct memory or there is a direct memory leak. The direct memory can be allocated by user code or some of its dependencies. In this case ‘taskmanager.memory.task.off-heap.size’ configuration option should be increased. Flink framework and its dependencies also consume the direct memory, mostly for network communication. The most of network memory is managed by Flink and should not result in out-of-memory error. In certain s

了解本专栏