[STORM-339] Severe memory leak to OOM when ackers disabled

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Abandoned
• Affects Version/s: 0.9.2-incubating
• Component/s: storm-core
• Assignee: Unassigned
• Reporter: Jiahong Li
• Created: 05/Jun/14 04:31
• Updated: 02/Jul/24 09:54
• Resolved: 02/Jul/24 09:54

Description

Without any ackers enabled, fast component will continuously leak memory and causing OOM problems when target component is slow. The OOM problem can be reproduced by running this fast-slow-topology:

https://github.com/Gvain/storm-perf-test/tree/fast-slow-topology

with command:

$ storm jar storm_perf_test-1.0.0-SNAPSHOT-jar-with-dependencies.jar com.yahoo.storm.perftest.Main --spout 1 --bolt 1 --workers 2 --testTime 600 --messageSize 6400

And the worker childopts with -Xms2g -Xmx2g -Xmn512m ....

At the same time, the executed count of target component is far behind from the emitted count of source component. I guess it could be that netty client is buffering too much messages in its message_queue as target component sends back OK/Failure Response too slowly.

Issue Links

• is duplicated by: STORM-387 Memory leak in worker