物理内存使用率太高 [英] Physical memory usage is too high
问题描述
当我尝试使用风暴在本地模式下运行拓扑时出现此错误
mvn compile exec:java -Dexec .classpathScope = compile -Dexec.mainClass = my.Topology
错误是
错误backtype.storm.util - 异步循环死了!
java.lang.OutOfMemoryError:物理内存使用率太高:physicalBytes = 3G> maxPhysicalBytes = 3G
我该如何解决?我不知道应该增加哪个物理内存!如果我在生产模式下运行拓扑,这个错误会消失吗?
UPDATE
物理内存阵列
位置:系统板或主板
使用:系统内存
纠错类型:无
最大容量:32 GB
错误信息句柄:0x0019
设备数量:4
我也在使用Apache Storm和JavaCV(OpenCV)。我有两个拓扑,第二个拓扑在这个过程中有两个螺栓,一个用于将视频分成帧,另一个用于检测面孔。
我有同样的问题:
2017-08-02 11:19:18.578 oasutil Thread-5-OpenCVBolt-executor [3 3] [ ERROR]
异步循环死了!
java.lang.OutOfMemoryError:物理内存使用率太高:physicalBytes = 1G> maxPhysicalBytes = 1G
at org.bytedeco.javacpp.Pointer.deallocator(Pointer.java:562)〜[stormjar.jar:?]
at org.bytedeco.javacpp.helper.opencv_core $ AbstractCvMemStorage.create (opencv_core.java:1649)〜[stormjar.jar:?]
at org.bytedeco.javacpp.helper.opencv_core $ AbstractCvMemStorage.create(opencv_core.java:1658)~ [stormjar.jar:?] $ b OpenCVBolt.detect上的$ b(OpenCVBolt.java :)〜[airjar.jar:?]
在OpenCVBolt.execute(OpenCVBolt.java:104)〜[stormjar.jar:?]
at org .apache.storm.daemon.executor $ fn__4973 $ tuple_action_fn__4975.invoke(executor.clj:727)〜[storm-core-1.0.3.jar:1.0.3]
org.apache.storm.daemon。执行者$ mk_task_receiver $ fn__4894.invoke(executor.clj:459)〜[storm-core-1.0.3.jar:1.0.3]
at org.apache.storm.disruptor $ clojure_handler $ reify__4409.onEvent(disruptor .clj:40)〜[storm-core-1.0.3.jar:1.0.3]
org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:453)〜[storm-core- 1.0.3.jar:1.0.3]
我是能够解决它。我不知道你是否使用JavaCV来处理视频和图像。如果是这样,并且您正在使用Maven,请确保在pom.xml中使用JavaCV 1.3.2版:
<依赖性>
< groupId> org.bytedeco< / groupId>
< artifactId> javacv< / artifactId>
< version> 1.3.2< / version>
< / dependency>
然后,您需要在 prepare()<中应用以下行你的博尔特中的/ code>方法来改变maxPhysicalBytes的属性。
System.setProperty(org.bytedeco。 javacpp.maxphysicalbytes,0);
System.setProperty(org.bytedeco.javacpp.maxbytes,0);
这对我有用。错误消失了。我希望这可以帮到你。
更新
@Override
public void prepare(Map conf,TopologyContext context,OutputCollector collector){
System.setProperty(org.bytedeco.javacpp.maxphysicalbytes,0);
System.setProperty(org.bytedeco.javacpp.maxbytes,0);
_collector = collector;
}
I got this error when I tried to run topology in local mode with storm using
mvn compile exec:java -Dexec.classpathScope=compile -Dexec.mainClass=my.Topology
the error is
ERROR backtype.storm.util - Async loop died!
java.lang.OutOfMemoryError: Physical memory usage is too high: physicalBytes = 3G > maxPhysicalBytes = 3G
How can I solve it? I don't know which Physical memory I should increase ! and if I run the topology in production mode, will this error be disappeared?
UPDATE
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 32 GB
Error Information Handle: 0x0019
Number Of Devices: 4
I'm also using Apache Storm with JavaCV (OpenCV). I have two Topologies, and the second Topology on the process has two bolts, one for split a video into frames, and another bolt for detecting faces.
I had the same issue:
2017-08-02 11:19:18.578 o.a.s.util Thread-5-OpenCVBolt-executor[3 3] [ERROR]
Async loop died!
java.lang.OutOfMemoryError: Physical memory usage is too high: physicalBytes = 1G > maxPhysicalBytes = 1G
at org.bytedeco.javacpp.Pointer.deallocator(Pointer.java:562) ~[stormjar.jar:?]
at org.bytedeco.javacpp.helper.opencv_core$AbstractCvMemStorage.create(opencv_core.java:1649) ~[stormjar.jar:?]
at org.bytedeco.javacpp.helper.opencv_core$AbstractCvMemStorage.create(opencv_core.java:1658) ~[stormjar.jar:?]
at OpenCVBolt.detect(OpenCVBolt.java:30) ~[stormjar.jar:?]
at OpenCVBolt.execute(OpenCVBolt.java:104) ~[stormjar.jar:?]
at org.apache.storm.daemon.executor$fn__4973$tuple_action_fn__4975.invoke(executor.clj:727) ~[storm-core-1.0.3.jar:1.0.3]
at org.apache.storm.daemon.executor$mk_task_receiver$fn__4894.invoke(executor.clj:459) ~[storm-core-1.0.3.jar:1.0.3]
at org.apache.storm.disruptor$clojure_handler$reify__4409.onEvent(disruptor.clj:40) ~[storm-core-1.0.3.jar:1.0.3]
at org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:453) ~[storm-core-1.0.3.jar:1.0.3]
I was able to solve it. I don't know if you are using JavaCV to work with video and images. If so, and you are working with Maven, make sure you work with JavaCV version 1.3.2 in your pom.xml:
<dependency>
<groupId>org.bytedeco</groupId>
<artifactId>javacv</artifactId>
<version>1.3.2</version>
</dependency>
Then, you need to apply the following lines in the prepare()
method in your Bolt to change the property of maxPhysicalBytes.
System.setProperty("org.bytedeco.javacpp.maxphysicalbytes", "0");
System.setProperty("org.bytedeco.javacpp.maxbytes", "0");
That's work for me. The error has disappeared. I hope this helps you.
UPDATE
@Override
public void prepare(Map conf, TopologyContext context, OutputCollector collector) {
System.setProperty("org.bytedeco.javacpp.maxphysicalbytes", "0");
System.setProperty("org.bytedeco.javacpp.maxbytes", "0");
_collector = collector;
}
这篇关于物理内存使用率太高的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!