Flink异常问题提总结

最新推荐文章于 2024-09-27 10:21:47 发布
最新推荐文章于 2024-09-27 10:21:47 发布
阅读量1.3w 收藏 3
点赞数 2
分类专栏： Flink Flink
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/u012164361/article/details/89674155
版权

Flink在执行过程中突然异常退出

Sink: time-kafka(1/1) switched to SCHEDULED
04/29/2019 10:10:20     Job execution switched to status FAILING.
org.apache.flink.runtime.jobmanager.scheduler.NoResourceAvailableException: Not enough free slots available to run the job. You can decrease the operator parallelism or increase thenumber of slots per TaskManager in the configuration. Task to schedule: < Attempt #10 (Source: source -> (Filter, Timestamps/Watermarks -> Filter) (12/12)) @ (unassigned) - [SCHEDULED] > with groupID < d460da9a057758d795825417554f0e72 > in sharing group < SlotSharingGroup [d460da9a057758d795825417554f0e72, 0f5d1bbb1c312ef7bcca697263389b15, 3b928584ed2bd5c041cea2f3dba3aa0e, a57d18a89c6c239247f95ebb9819ce1e, dabc4aa3951942f45c2de75c800930c3] >. Resources available to scheduler: Number of instances=11, total number of slots=11, available slots=0
        at org.apache.flink.runtime.jobmanager.scheduler.Scheduler.scheduleTask(Scheduler.java:263)
        at org.apache.flink.runtime.jobmanager.scheduler.Scheduler.allocateSlot(Scheduler.java:142)
        at org.apache.flink.runtime.executiongraph.Execution.lambda$allocateAndAssignSlotForExecution$1(Execution.java:440)
        at java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:981)
        at java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2124)
        at org.apache.flink.runtime.executiongraph.Execution.allocateAndAssignSlotForExecution(Execution.java:438)
        at org.apache.flink.runtime.executiongraph.ExecutionJobVertex.allocateResourcesForAll(ExecutionJobVertex.java:503)
        at org.apache.flink.runtime.executiongraph.ExecutionGraph.scheduleEager(ExecutionGraph.java:891)
        at org.apache.flink.runtime.executiongraph.ExecutionGraph.scheduleForExecution(ExecutionGraph.java:845)
        at org.apache.flink.runtime.executiongraph.ExecutionGraph.restart(ExecutionGraph.java:1193)
        at org.apache.flink.runtime.executiongraph.restart.ExecutionGraphRestartCallback.triggerFullRecovery(ExecutionGraphRestartCallback.java:59)
        at org.apache.flink.runtime.executiongraph.restart.FixedDelayRestartStrategy$1.run(FixedDelayRestartStrategy.java:68)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        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)
04/29/2019 10:10:20     Source: source -> (Filter, Timestamps/Watermarks -> Filter)(1/12) switched to CANCELED
04/29/2019 10:10:20     Source: source -> (Filter, Timestamps/Watermarks -> Filter)(2/12) switched to CANCELED
04/29/2019 10:10:20     Source: source -> (Filter, Timestamps/Watermarks -> Filter)(3/12) switched to CANCELED
04/29/2019 10:10:20     Source: source -> (Filter, Timestamps/Watermarks -> Filter)(4/12) switched to CANCELED
04/29/2019 10:10:20     Source: source -> (Filter, Timestamps/Watermarks -> Filter)(5/12) switched to CANCELED
04/29/2019 10:10:20     Source: source -> (Filter, Timestamps/Watermarks -> Filter)(6/12) switched to CANCELED
04/29/2019 10:10:20     Source: source -> (Filter, Timestamps/Watermarks -> Filter)(7/12) switched to CANCELED
04/29/2019 10:10:20     Source: source -> (Filter, Timestamps/Watermarks -> Filter)(8/12) switched to CANCELED
04/29/2019 10:10:20     Source: source -> (Filter, Timestamps/Watermarks -> Filter)(9/12) switched to CANCELED
04/29/2019 10:10:20     Source: source -> (Filter, Timestamps/Watermarks -> Filter)(10/12) switched to CANCELED
04/29/2019 10:10:20     Source: source -> (Filter, Timestamps/Watermarks -> Filter)(11/12) switched to CANCELED
04/29/2019 10:10:20     Source: source -> (Filter, Timestamps/Watermarks -> Filter)(12/12) switched to CANCELED
04/29/2019 10:10:20     counter(1/12) switched to CANCELED
04/29/2019 10:10:20     counter(2/12) switched to CANCELED
04/29/2019 10:10:20     counter(3/12) switched to CANCELED
04/29/2019 10:10:20     counter(4/12) switched to CANCELED
04/29/2019 10:10:20     counter(5/12) switched to CANCELED
04/29/2019 10:10:20     counter(6/12) switched to CANCELED
04/29/2019 10:10:20     counter(7/12) switched to CANCELED
04/29/2019 10:10:20     counter(8/12) switched to CANCELED
04/29/2019 10:10:20     counter(9/12) switched to CANCELED
04/29/2019 10:10:20     counter(10/12) switched to CANCELED
04/29/2019 10:10:20     counter(11/12) switched to CANCELED
04/29/2019 10:10:20     counter(12/12) switched to CANCELED
04/29/2019 10:10:20     Sink: counter-kafka(1/1) switched to CANCELED
04/29/2019 10:10:20     timer1(1/12) switched to CANCELED
04/29/2019 10:10:20     timer1(2/12) switched to CANCELED
04/29/2019 10:10:20     timer1(3/12) switched to CANCELED
04/29/2019 10:10:20     timer1(4/12) switched to CANCELED
04/29/2019 10:10:20     timer1(5/12) switched to CANCELED
04/29/2019 10:10:20     timer1(6/12) switched to CANCELED
04/29/2019 10:10:20     timer1(7/12) switched to CANCELED
04/29/2019 10:10:20     timer1(8/12) switched to CANCELED
04/29/2019 10:10:20     timer1(9/12) switched to CANCELED
04/29/2019 10:10:20     timer1(10/12) switched to CANCELED
04/29/2019 10:10:20     timer1(11/12) switched to CANCELED
04/29/2019 10:10:20     timer1(12/12) switched to CANCELED
04/29/2019 10:10:20     Sink: time-kafka(1/1) switched to CANCELED
04/29/2019 10:10:20     Job execution switched to status FAILED.
2019-04-29 10:10:20,666 INFO  org.apache.flink.yarn.YarnClusterClient                       - Sending shutdown request to the Application Master
2019-04-29 10:10:20,666 INFO  org.apache.flink.yarn.YarnClusterClient                       - Start application client.
2019-04-29 10:10:20,859 INFO  org.apache.flink.yarn.ApplicationClient                       - Notification about new leader address akka.tcp://flink@emr-worker-3.cluster-70637:36513/user/jobmanager with session ID 00000000-0000-0000-0000-000000000000.
2019-04-29 10:10:20,868 INFO  org.apache.flink.yarn.ApplicationClient                       - Sending StopCluster request to JobManager.
2019-04-29 10:10:20,869 INFO  org.apache.flink.yarn.ApplicationClient                       - Received address of new leader akka.tcp://flink@emr-worker-3.cluster-70637:36513/user/jobmanager with session ID 00000000-0000-0000-0000-000000000000.
2019-04-29 10:10:20,869 INFO  org.apache.flink.yarn.ApplicationClient                       - Disconnect from JobManager null.
2019-04-29 10:10:20,872 INFO  org.apache.flink.yarn.ApplicationClient                       - Trying to register at JobManager akka.tcp://flink@emr-worker-3.cluster-70637:36513/user/jobmanager.
2019-04-29 10:10:20,878 INFO  org.apache.flink.yarn.ApplicationClient                       - Successfully registered at the ResourceManager using JobManager Actor[akka.tcp://flink@emr-worker-3.cluster-70637:36513/user/jobmanager#-153942343]
2019-04-29 10:10:21,888 INFO  org.apache.flink.yarn.ApplicationClient                       - Sending StopCluster request to JobManager.
2019-04-29 10:10:23,747 INFO  org.apache.flink.yarn.YarnClusterClient                       - Application application_1556227576661_0231 finished with state FINISHED and final stateSUCCEEDED at 1556503821989
2019-04-29 10:10:23,747 INFO  org.apache.flink.yarn.YarnClusterClient                       - YARN Client is shutting down
2019-04-29 10:10:23,911 INFO  org.apache.flink.yarn.ApplicationClient                       - Stopped Application client.
2019-04-29 10:10:23,911 INFO  org.apache.flink.yarn.ApplicationClient                       - Disconnect from JobManager Actor[akka.tcp://flink@emr-worker-3.cluster-70637:36513/user/jobmanager#-153942343].
2019-04-29 10:10:25.282 [main] ERROR c.a.e.f.a.j.l.impl.CommonShellJobLauncherImpl - [FNI-09F180DD19111D0F_0] Failed to execute command, exit code=1
2019-04-29 10:10:25.296 [main] INFO  c.a.e.f.a.j.l.impl.CommonShellJobLauncherImpl - [FNI-09F180DD19111D0F_0] Finished command line, exit code=1.
Mon Apr 29 10:10:25 CST 2019 [JobLauncherRunner] INFO Closing job launcher ...
2019-04-29 10:10:25.298 [main] INFO  c.a.emr.flow.agent.jobs.launcher.JobLauncherBase - [FNI-09F180DD19111D0F_0] Closing ...
2019-04-29 10:10:25.298 [main] INFO  c.a.e.f.a.j.l.impl.CommonShellJobLauncherImpl - [FNI-09F180DD19111D0F_0] Stopping command executor ...
Mon Apr 29 10:10:25 CST 2019 [YarnJobLauncherAM] INFO Closing launcher am ...
Mon Apr 29 10:10:25 CST 2019 [YarnJobLauncherAM] INFO Emr flow launcher is quit.
Exception in thread "main" java.lang.reflect.UndeclaredThrowableException
        at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1672)
        at com.aliyun.emr.flow.agent.jobs.launcher.yarn.YarnJobLauncherAM.doMain(YarnJobLauncherAM.java:72)
        at com.aliyun.emr.flow.agent.jobs.launcher.yarn.YarnJobLauncherAM.main(YarnJobLauncherAM.java:137)
Caused by: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at com.aliyun.emr.flow.agent.jobs.launcher.JobLauncherRunner.run(JobLauncherRunner.java:59)
        at com.aliyun.emr.flow.agent.jobs.launcher.yarn.YarnJobLauncherAM.launchJob(YarnJobLauncherAM.java:104)
        at com.aliyun.emr.flow.agent.jobs.launcher.yarn.YarnJobLauncherAM.access$000(YarnJobLauncherAM.java:32)
        at com.aliyun.emr.flow.agent.jobs.launcher.yarn.YarnJobLauncherAM$1.run(YarnJobLauncherAM.java:75)
        at com.aliyun.emr.flow.agent.jobs.launcher.yarn.YarnJobLauncherAM$1.run(YarnJobLauncherAM.java:72)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:422)
        at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
        ... 2 more
Caused by: com.aliyun.emr.flow.agent.common.exceptions.EmrFlowRuntimeException: ###[E10012,JOB]:  Execute job FNI-09F180DD19111D0F_0 failed, exit code: 1, message: .
        at com.aliyun.emr.flow.agent.common.utils.Throwables.propagate(Throwables.java:68)
        at com.aliyun.emr.flow.agent.jobs.launcher.impl.CommonShellJobLauncherImpl.doLaunch(CommonShellJobLauncherImpl.java:221)
        at com.aliyun.emr.flow.agent.jobs.launcher.impl.CommonShellJobLauncherImpl.launch(CommonShellJobLauncherImpl.java:207)
        ... 14 more
2019-04-29 10:10:25.613 [Shutdown-FNI-09F180DD19111D0F_0] INFO  c.a.emr.flow.agent.jobs.launcher.JobLauncherBase - [FNI-09F180DD19111D0F_0] Call shutdown hook.
2019-04-29 10:10:25.614 [Shutdown-FNI-09F180DD19111D0F_0] INFO  c.a.emr.flow.agent.jobs.launcher.JobLauncherBase - [FNI-09F180DD19111D0F_0] Closing ...
2019-04-29 10:10:25.614 [Shutdown-FNI-09F180DD19111D0F_0] INFO  c.a.emr.flow.agent.jobs.launcher.JobLauncherBase - [FNI-09F180DD19111D0F_0] This launcher is closed already, skip.

Flink参数设置slot数量增加,Flink无法启动的bug

/2019 14:07:03     counter(62/96) switched to FAILED
java.io.IOException: Insufficient number of network buffers: required 96, but only 25 available. The total number of network buffers is currently set to 2048 of 32768 bytes each. You can increase this number by setting the configuration keys 'taskmanager.network.memory.fraction', 'taskmanager.network.memory.min', and 'taskmanager.network.memory.max'.
        at org.apache.flink.runtime.io.network.buffer.NetworkBufferPool.createBufferPool(NetworkBufferPool.java:257)
        at org.apache.flink.runtime.io.network.NetworkEnvironment.registerTask(NetworkEnvironment.java:235)
        at org.apache.flink.runtime.taskmanager.Task.run(Task.java:618)
        at java.lang.Thread.run(Thread.java:748)

04/29/2019 14:07:03     counter(63/96) switched to FAILED
java.io.IOException: Insufficient number of network buffers: required 96, but only 26 available. The total number of network buffers is currently set to 2048 of 32768 bytes each. You can increase this number by setting the configuration keys 'taskmanager.network.memory.fraction', 'taskmanager.network.memory.min', and 'taskmanager.network.memory.max'.
        at org.apache.flink.runtime.io.network.buffer.NetworkBufferPool.createBufferPool(NetworkBufferPool.java:257)
        at org.apache.flink.runtime.io.network.NetworkEnvironment.registerTask(NetworkEnvironment.java:235)
        at org.apache.flink.runtime.taskmanager.Task.run(Task.java:618)
        at java.lang.Thread.run(Thread.java:748)

04/29/2019 14:07:03     timer1(57/96) switched to FAILED
java.io.IOException: Insufficient number of network buffers: required 96, but only 26 available. The total number of network buffers is currently set to 2048 of 32768 bytes each. You can increase this number by setting the configuration keys 'taskmanager.network.memory.fraction', 'taskmanager.network.memory.min', and 'taskmanager.network.memory.max'.
        at org.apache.flink.runtime.io.network.buffer.NetworkBufferPool.createBufferPool(NetworkBufferPool.java:257)
        at org.apache.flink.runtime.io.network.NetworkEnvironment.registerTask(NetworkEnvironment.java:235)
        at org.apache.flink.runtime.taskmanager.Task.run(Task.java:618)
        at java.lang.Thread.run(Thread.java:748)

04/29/2019 14:07:03     Job execution switched to status FAILING.
java.io.IOException: Insufficient number of network buffers: required 96, but only 25 available. The total number of network buffers is currently set to 2048 of 32768 bytes each. You can increase this number by setting the configuration keys 'taskmanager.network.memory.fraction', 'taskmanager.network.memory.min', and 'taskmanager.network.memory.max'.
        at org.apache.flink.runtime.io.network.buffer.NetworkBufferPool.createBufferPool(NetworkBufferPool.java:257)
        at org.apache.flink.runtime.io.network.NetworkEnvironment.registerTask(NetworkEnvironment.java:235)
        at org.apache.flink.runtime.taskmanager.Task.run(Task.java:618)
        at java.lang.Thread.run(Thread.java:748)```
解决:调整Flink里面flink-conf.yaml里面的新增参数增加可支持的slot数量


taskmanager.network.memory.fraction: 0.1
taskmanager.network.memory.min: 268435456
taskmanager.network.memory.max: 4294967296
梦想成真那天
关注
专栏目录
Flink报错：java.io.IOException: Insufficient number of network buffers
九师兄
12-03 3292
1.美图 2.概述 Flink的master与worker进程有不同的内存需求。Master进程主要管理计算资源（也就是ResourceManager）以及协调applications的执行（也就是JobManager）。而worker进程的需要进行各类计算并处理数据（可能是大量数据）。 一般来说，master进程的内存需求并不是特别大。默认情况下，它使用1GB的JVM堆内存。如果一个master...
Flink报错：缺少网络缓冲区
AlianBlank的博客
08-12 721
Insufficient number of network buffers”（缺少网络缓冲区）错误是在 Flink 运行作业时可能会遇到的一个问题。本文介绍了这个错误的原因，并提供了调整任务并行度、增加网络缓冲区数量以及优化算子内存使用的解决方案。希望能够帮助读者排除这个问题，并顺利运行 Flink 作业。如果问题仍然存在，建议查看 Flink 官方文档或者寻求相关社区的支持。
flink启动同步任务后全部失败，报错：NoResourceAvailableException: Could not acquire the minimum required resources.
最新发布
weixin_42442805的博客
09-27 599
修改flink的配置文件 ，目录是 flink-1.18.0/conf/中flink-conf-yaml的jobmanager.memory.process.size和taskmanager.memory.flink.size。注意：实际修改后还是报错，发现配置前面多了个空格⊙﹏⊙，删掉后重启服务成功。然后重启flink服务 ./bin/stop-cluster.sh，重启同步任务。
Flink任务报：Could not allocate the required slot within slot request timeout.
你的代码有灵魂吗？
07-14 1万+
问题描述 问题描述：Flink job提交到集群上跑，提交成功了，但是每次都是等很久之后就失败了，一直报：Could not allocate the required slot within slot request timeout. Please make sure that the cluster has enough resources. 此外，跑了Spark任务和Flink官方的批处理的WordCount例子都是可以跑成功的； 具体错误 [root@BigData04 f..
Flink 1.13 写 HDFS 任务异常分析
jdx2008678的专栏
10-25 1421
任务是基于Flink 1.13 版本java api 实现的，主要功能是将业务数据写到 hdfs 上
【Flink】Flink 消费kafka报错 AMRMClientAsyncImpl Interrupted while waiting for queue InterruptedException
九师兄
06-27 3193
1.背景 一个flink etl程序，读取一个kafka集群的数据，到两外一个集群，然后报错 2020-06-06 15:56:00 PM [Thread: flink-akka.actor.default-dispatcher-20][ Class:org.apache.flink.runtime.executiongraph.ExecutionGraph] INFO:Source: com.dbapp.ailpha.topic.securityalarm.copy -> filter_2 -&gt
Flink知识点总结 Flink简介
热门推荐
cliper9768的博客
10-10 3万+
flink记录
Flink大数据量调优思路总结（二）
击水三千里的专栏
04-10 686
数据量越大越需要对flink进行精细化调优
Flink SQL操作Hudi并同步Hive使用总结
主要分享大数据相关的知识，如Spark、Hudi
11-01 7413
记录总结自己第一次如何使用Flink SQL读写Hudi并同步Hive，以及遇到的问题及解决过程。关于Flink SQL客户端如何使用可以参考：Flink SQL 客户端查询Hive配置及问题解决Flink 1.14.3 Hudi 0.12.0/0.12.1本文采用Flink yarn-session模式，不会的可以参考之前的文章。下载地址：https://repo1.maven.org/maven2/org/apache/hudi/hudi-flink1.14-bundle/0.12.1/hudi-fli
flink实战--flink原理解析
阿华田的博客
09-30 2万+
Flink出现的背景 我们知道目前流处理的主要流行的计算引擎有，Storm，SparkStreaming。但是这个两个计算引擎都有自己的局限性。Storm实现了低延迟，但是目前还没有实现高吞吐，也不能在故障发生的时候准确的处理计算状态（将数据从一个事件保存到另一个事件的，这些保留下来的是数据较计算状态），同时也不能实现exactly-once。SparkStreaming通过微批处理方法............
[Flink]一、Flink1.13
weixin_44428807的博客
07-01 1069
1. Flink简介1.1 Flink的起源和设计理念flink项目的核心目标：数据流上的有状态计算（Stateful Computations over Data Streams)。时间驱动：来一个事件处理一个事件；流处理的流水线；流&批数据分析具体定位是：Apache Flink 是一个框架和分布式处理引擎，用于对无界和有界数据流进行有状态计算。Flink 被设计在所有常见的集群环境中运行，以内存执行速度和任意规模来执行计算。1.2 Flink的应用。
flink 问题记录
Jhon_yh的博客
06-09 1934
文章目录1. Caused by: java.lang.UnsatisfiedLinkError: org.apache.hadoop.util.NativeCrc32.nativeComputeChunkedSums(IILjava/nio/ByteBuffer;ILjava/nio/ByteBuffer;IILjava/lang/String;JZ)V原因 1. Caused by: java.lang.UnsatisfiedLinkError: org.apache.hadoop.util.Nat
flink常见故障排除
第一片心意的博客
10-16 6868
flink常见故障排除
关于 flink 执行SocketWindowWordCount程序报错 ：Job execution failed.
qq_34841911的博客
01-28 6834
我自个第一次执行flink 的SocketWindowWordCount 程序是，报一个:Caused by: org.apache.flink.runtime.jobmanager.scheduler.NoResourceAvailableException: Not enough free slots available to run the job. You can decrease the
flink checkpoint 恢复_Flink 从Checkpoint中恢复作业
weixin_39977642的博客
12-27 2357
Flink 1.11 版本1. 配置如果我们的任务已经执行很长时间，突然遇到故障停止，那么中间过程处理结果就会全部丢失，重启后需要重新从上一次开始的位置消费，这会花费我们很长的时间。这种结局显示我们不能接受，我们希望的是作业在故障失败重启后能保留之前的状态并能从失败的位置继续消费。可以通过如下配置保存处理状态：final StreamExecutionEnvironment env = ...
Flink链接kafka并解析Json文件(一)
morsunlight的博客
01-21 2240
背景:某小型互联网公司每日的疫情填报 Flink消费Kafka中的Json数据 遇到的问题:Flink的jar包上传Flink服务器报错 web页面报错: 2021-01-1910:26:42,437INFOorg.apache.kafka.common.utils.AppInfoParser-Kafkaversion:0.11.0.2 2021-01-1910:26:42,438INFOorg.apache.kafka.common.ut...
java join 异常_java-无法运行flink示例程序， join被拒绝
weixin_39672979的博客
03-06 388
root@maple-PC:/home/maple/Downloads/flink-1.4.2# ./bin/flink run examples/streaming/SocketWindowWordCount.jar --port 9000Cluster configuration: Standalone cluster with JobManager at localhost/127.0.0....
Flink 非对齐Unaligned的checkpoint（源码分析）
m0_56069948的博客
01-13 737
Python微信订餐小程序课程视频 https://edu.csdn.net/course/detail/36074 Python实战量化交易理财系统 https://edu.csdn.net/course/detail/35475 本文源码基于flink1.14 在帮助用户排查任务的时候，经常会发现部分task处理的慢，在Exactly once语义时需要等待快照的对齐而白白柱塞的情况 在flink1.11版本引入了非对齐的checkpoint，来解决这种柱塞问题，所以来看看这个新特性的源码是如何实现的
flink 常用异常错误解析
wppwpp1的专栏
02-09 1701
IllegalConfigurationException 如果您看到从TaskExecutorProcessUtils或JobManagerProcessUtils抛出IllegalConfigurationException，则通常表明存在无效的配置值（例如，负的内存大小，大于1的分数等）或配置冲突。检查与异常消息中提到的内存组件相关的文档章节或配置选项。 OutOfMemoryError：Java堆空间 异常通常表明JVM堆太小。您可以尝试通过增加总内存来增加JVM堆大小。您也可以直接增..
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值