Flink1.13 yarn-cluster运行内存分配报错

最新推荐文章于 2026-06-07 09:25:20 发布
原创 最新推荐文章于 2026-06-07 09:25:20 发布 · 1.1k 阅读 · 2 ·
本内容遵循CC 4.0 BY-SA版权协议
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
收录于
Flink

当前文章被收录于：

Flink
1 篇文章 0 人学习
订阅专栏 查看详情
在将 Flink 从 1.12 升级到 1.13 的过程中，遇到 per-job 模式的提交报错，错误信息为 'Neither virtual-memory nor physical-memory monitoring is needed. Not running the monitor-thread'。1.12 版本的 per-job 提交正常，而 1.13 的 session 模式提交没有问题。已经尝试修改 `yarn-site.xml` 中的内存检查配置为 false，以及设置最大内存、最小内存和虚拟内存比例，但问题依旧存在，寻求解决方案。

【求助贴】

flink1.12升级1.13的时候报错，Neither virutal-memory nor physical-memory monitoring is needed. Not running the monitor-thread

现状： 1.12可以正常per-job模式提交，1.13可以正常session模式提交，只有1.13的per-job提交报错。报错截图和内容贴出，求大佬解惑。提供思路也行，万分感谢！！！

2021-07-19 23:11:33,647 INFO org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor: Exception from container-launch.
2021-07-19 23:11:33,647 INFO org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor: Container id: container_1626608338288_0034_02_000001
2021-07-19 23:11:33,647 INFO org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor: Exit code: 239
2021-07-19 23:11:33,647 INFO org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor: Stack trace: ExitCodeException exitCode=239:
2021-07-19 23:11:33,647 INFO org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor:       at org.apache.hadoop.util.Shell.runCommand(Shell.java:585)
2021-07-19 23:11:33,647 INFO org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor:       at org.apache.hadoop.util.Shell.run(Shell.java:482)
2021-07-19 23:11:33,647 INFO org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor:       at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:776)
2021-07-19 23:11:33,647 INFO org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor:       at org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.launchContainer(DefaultContainerExecutor.java:212)
2021-07-19 23:11:33,647 INFO org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor:       at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:302)
2021-07-19 23:11:33,647 INFO org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor:       at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:82)
2021-07-19 23:11:33,647 INFO org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor:       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
2021-07-19 23:11:33,647 INFO org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor:       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
2021-07-19 23:11:33,647 INFO org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor:       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
2021-07-19 23:11:33,647 INFO org.apache.hadoop.yarn.server.nodemanager.ContainerExecutor:       at java.lang.Thread.run(Thread.java:748)
2021-07-19 23:11:33,647 WARN org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch: Container exited with a non-zero exit code 239
2021-07-19 23:11:33,647 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl: Container container_1626608338288_0034_02_000001 transitioned from RUNNING to EXITED_WITH_FAILURE
2021-07-19 23:11:33,647 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch: Cleaning up container container_1626608338288_0034_02_000001
2021-07-19 23:11:33,665 INFO org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor: Deleting absolute path : /export/server/hadoop-2.7.5/hadoopDatas/tempDatas/nm-local-dir/usercache/root/appcache/application_1626608338288_0034/container_1626608338288_0034_02_000001
2021-07-19 23:11:33,665 WARN org.apache.hadoop.yarn.server.nodemanager.NMAuditLogger: USER=root OPERATION=Container Finished - Failed   TARGET=ContainerImpl    RESULT=FAILURE  DESCRIPTION=Container failed with state: EXITED_WITH_FAILURE    APPID=application_1626608338288_0034    CONTAINERID=container_1626608338288_0034_02_000001
2021-07-19 23:11:33,665 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl: Container container_1626608338288_0034_02_000001 transitioned from EXITED_WITH_FAILURE to DONE
2021-07-19 23:11:33,665 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.application.ApplicationImpl: Removing container_1626608338288_0034_02_000001 from application application_1626608338288_0034
2021-07-19 23:11:33,665 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl: Neither virutal-memory nor physical-memory monitoring is needed. Not running the monitor-thread
2021-07-19 23:11:33,665 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.logaggregation.AppLogAggregatorImpl: Considering container container_1626608338288_0034_02_000001 for log-aggregation
2021-07-19 23:11:33,665 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices: Got event CONTAINER_STOP for appId application_1626608338288_0034
2021-07-19 23:12:20,712 INFO SecurityLogger.org.apache.hadoop.ipc.Server: Auth successful for appattempt_1626608338288_0034_000007 (auth:SIMPLE)
2021-07-19 23:12:20,716 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl: Start request for container_1626608338288_0034_07_000001 by user root
2021-07-19 23:12:20,716 INFO org.apache.hadoop.yarn.server.nodemanager.NMAuditLogger: USER=root IP=10.10.10.230 OPERATION=Start Container Request       TARGET=ContainerManageImpl      RESULT=SUCCESS  APPID=application_1626608338288_0034    CONTAINERID=container_1626608338288_0034_07_000001
2021-07-19 23:12:20,716 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.application.ApplicationImpl: Adding container_1626608338288_0034_07_000001 to application application_1626608338288_0034
2021-07-19 23:12:20,717 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl: Container container_1626608338288_0034_07_000001 transitioned from NEW to LOCALIZING
2021-07-19 23:12:20,717 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices: Got event CONTAINER_INIT for appId application_1626608338288_0034
2021-07-19 23:12:20,717 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl: Container container_1626608338288_0034_07_000001 transitioned from LOCALIZING to LOCALIZED
2021-07-19 23:12:20,733 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl: Container container_1626608338288_0034_07_000001 transitioned from LOCALIZED to RUNNING
2021-07-19 23:12:20,733 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl: Neither virutal-memory nor physical-memory monitoring is needed. Not running the monitor-thread
2021-07-19 23:12:20,735 INFO org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor: launchContainer: [bash, /export/server/hadoop-2.7.5/hadoopDatas/tempDatas/nm-local-dir/usercache/root/appcache/application_1626608338288_0034/container_1626608338288_0034_07_000001/default_container_executor.sh]
2021-07-19 23:12:32,641 WARN org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor: Exit code from container container_1626608338288_0034_07_000001 is : 239
2021-07-19 23:12:32,641 WARN org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor: Exception from container-launch with container ID: container_1626608338288_0034_07_000001 and exit code: 239
ExitCodeException exitCode=239:
        at org.apache.hadoop.util.Shell.runCommand(Shell.java:585)
        at org.apache.hadoop.util.Shell.run(Shell.java:482)
        at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:776)
        at org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.launchContainer(DefaultContainerExecutor.java:212)
        at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:302)
        at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:82)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

在这里插入图片描述

已做尝试
1、yarn-site.xml 内存检查改为false。

<property>
        <name>yarn.nodemanager.vmem-check-enabled</name>
        <value>false</value>
    </property>

2、配置最大内存，最小内存，虚拟内存占用物理内存比例。

    <property>
        <name>yarn.scheduler.maximum-allocation-mb</name>
        <value>20480</value>
    </property>
    <property>
        <name>yarn.scheduler.minimum-allocation-mb</name>
        <value>2048</value>
    </property>
    <property>
        <name>yarn.nodemanager.vmem-pmem-ratio</name>
        <value>5</value><!-- 默认2.1 -->
    </property>
flink实战--开发中常见的错误与问题
阿华田的博客
12-19 2万+
常见错误集 1.Checkpoint失败：Checkpoint expired before completing env.enableCheckpointing(1000L) val checkpointConf = env.getCheckpointConfig checkpointConf.setMinPauseBetweenCheckp...
Ambari 3.0+BigTop 3.3集群部署实战
docsz的博客
05-15 402
Ambari 3.0+BigTop 3.3集群部署
Flink sql 异常踩坑帖
m0_54932731的博客
02-25 1819
1.Static methods in interface require -target:jvm-1.8 解决方案：在pom中修改，参考：https://blog.csdn.net/YongDaiMe/article/details/108586263，在scala打包插件中增加-target ：jvm-1.8配置。 <plugin> <groupId>net.alchim31.maven</groupId> <artifactId>s
Container exited with a non-zero exit code 1. Error file: prelaunch.err.org.apache.hadoop.mapreduce.
热门推荐
colby_chenlun的博客
05-31 2万+
这两天闲的慌，装了一下新版本的HADOOP 3.2.1，的HA，装好之后，测试wordcount程序时报下面的错误 For more detailed output, check the application tracking page: http://hadoop102:8088/cluster/app/application_1590917926429_0002 Then click on links to logs of each attempt. . Failing the applicati
Hadoop 系列YARN：资源调度平台（YARN的命令）
weixin_33814685的博客
11-20 682
yarn命令的用法 [root@node1 ~]# yarn Usage: yarn [--config confdir] [COMMAND | CLASSNAME] CLASSNAME run the class named CLASSNAME or where COMMAND is one of: resou...
flink yarn ERROR Exit code: 239
wppwpp1的专栏
05-03 8443
1, flink on yarn模式运行一段时间后，报239错误,代码如下： 2，通过排除问题，发现checkpoint失败，导致程序异常退出，之前checkpoint时间是2分钟，修改成5分钟，在观察一段时间，看看是否有问题 ...
【Flink】集群环境下的搭建（Standalone 模式）
2403_86969226的博客
11-28 1989
Flink是目前开源社区中唯一一套集高吞吐、低延迟、高性能三者于一身的分布式流式数据处理框架，支持多种安装部署模式。主要包括以下几种‌1‌.Standalone 模式‌：这是独立运行的模式，不依赖任何外部的资源管理平台，只需要运行所有Flink组件服务。这种模式适合开发和测试环境‌。2‌.YARN 模式。
大数据（9b）Flink集群部署YARN模式
ArYe
07-14 665
文章目录
数据工程师实战指南：Hadoop、Spark、Flink等五大框架生产调优与避坑
最新发布
weixin_30772105的博客
06-07 724
大数据（Big Data）指在分布式环境下对海量、高速、多样数据进行采集、存储、计算与服务的系统性工程能力。其核心原理在于通过分而治之（Shuffle/Partition）、容错重试（Speculative Execution/Checkpointing）和统一资源调度（YARN/K8s）保障SLA。技术价值体现在降低TCO、提升分析时效性与支撑实时决策闭环。典型应用场景包括电商用户行为分析、金融风控实时拦截、IoT设备时序处理等。本文聚焦Hadoop、Spark、Flink、Hive、Storm五大高频框
YARN架构本质：资源抽象、调度解耦与容器化治理
weixin_30654583的博客
06-06 361
YARN是Hadoop生态的分布式资源治理核心，其本质并非传统意义的调度器，而是通过资源抽象（Container）、关注点分离（RM/AM/NM）和细粒度隔离（cgroups/Kerberos）构建的类操作系统级基础设施。它将物理资源转化为可计量、可配额、可审计的逻辑单元，支撑Spark/Flink等多引擎混部；其调度策略（如CapacityScheduler）实现租户级SLA保障与潮汐弹性，内存模型（heap + memoryOverhead + vmem-pmem-ratio）和CPU份额（vcores
PySpark MLlib 生产级二分类实战：从特征工程到模型部署
weixin_30263073的博客
06-05 327
在大数据场景下，分类任务已超越单机 scikit-learn 的能力边界，进入分布式机器学习工程化阶段。PySpark MLlib 作为 Spark 原生的 DataFrame-based 机器学习库，其核心价值在于将特征工程、模型训练与预测服务封装为可复用、可持久化、可调度的 Pipeline 流水线。它通过 StringIndexer 实现类别特征的鲁棒编码，借助 VectorAssembler 统一构建稀疏/稠密特征向量，并依托 StandardScaler 等 Transformer 保障训练与推理
Flink
weixin_51093408的博客
08-17 4420
问题1： flink Can''t call rollback when autocommit=true 解决： kafka的topic没有数据。 问题2： per-job模式运行报异常，global limit =2; local limit is =1 解决：hadoop依赖冲突。
【Flink】Flink exitCode=239
九师兄
04-25 2361
1.场景1 1.1 概述 checkpoint 设置3分钟 也失败 我申请的 资源是 -yqu realtime -yjm 1024 -ytm 2048 -ys 2
Flink任务提交问题汇总
微信搜：import_bigdata，大数据领域硬核原创作者
02-24 2219
全网最全大数据面试提升手册！flink 任务提交问题汇总1. 提交flink自带任务WordCount.jar遇到的问题：2. 提交flink 批处理任务时遇到的问题3. flink定时任务，mysql连接超时问题4. flink checkpoint 恢复失败5. yarn 增加并行任务数量配置6. 流处理flink程序在hadoop集群跑了一段时间莫名挂掉1. 提交flink自带任务WordC...
【YARN】问题汇总（持续更新）
lin86182824的博客
07-29 2983
1、TEZ一直卡主 原因是：集群的 mapreduce.map.cpu.vcores 改成了 4，hive 默认会使用这个参数作为 tez container 的 vcores。tez vcores 大于 1 时会导致无法正常启动 container，可以设置参数 hive.tez.cpu.vcores=1 来解决。 ......
Spark Stack trace: ExitCodeException
Logan_addoil的博客
01-18 480
Spark Stack trace: ExitCodeException exitCode=10
flink 运维中遇到的问题
h952520296的博客
03-03 9714
1. Java.lang.IllegalStateException: No Executor found. Please make sure to export the HADOOP_CLASSPATH environment variable or have hadoop in your classpath. For more information refer to the "Deployment" section of the official Apache Flink documentation.
spark开发问题汇总
盛源的博客
09-23 4827
1 可能导致内存溢出的聚合函数 1 错误代码 Container exited with a non-zero exit code 134. Error file: prelaunch.err. Last 4096 bytes of prelaunch.err 2 函数 collect_set 、 collect_list 3 原因 某个key值(null, unknown, 空串)过多, 被聚合的value值过多, 导致范围(数组超范围)超限; 3 解决方法 1) 调大内存 2) .
评论 5
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值