storm运行到一半就不继续计算了

Question

单机测试Storm，从rocketMq接收信息

刚刚启动的时候可以正常接收并计算数据，但是运行一段时间后就只接收数据而不计算了，求助各位大神！！

打印TicketInfo代表收到了对象，打印Bolt代表Spout发送到了Bolt进行计算

但是运行一段时间后，就只能打印的对象信息，而没有Bolt的计算的打印了，重启之后又可以继续计算，如此反复

每次出现如下信息就会发送上面的现象

19543 [timer] INFO  backtype.storm.daemon.nimbus - Setting new assignment for topology id position-1-1428982465: #backtype.storm.daemon.common.Assignment{:master-code-dir "C:\Users\AppData\Local\Temp\9c04c562-c065-4bc9-a1e6-3200fdd66acb\nimbus\stormdist\position-1-1428982465", :node->host {"cb0255e3-3fba-439f-b485-02accfb17fed" "user"}, :executor->node+port {[3 3] ["cb0255e3-3fba-439f-b485-02accfb17fed" 1024], [4 4] ["cb0255e3-3fba-439f-b485-02accfb17fed" 1024], [2 2] ["cb0255e3-3fba-439f-b485-02accfb17fed" 1024], [1 1] ["cb0255e3-3fba-439f-b485-02accfb17fed" 1024]}, :executor->start-time-secs {[4 4] 1428982474, [1 1] 1428982474, [2 2] 1428982474, [3 3] 1428982474}}

附上部分日志

SLF4J: Class path contains multiple SLF4J bindings.

SLF4J: Found binding in [jar:file:/E:/MyEclipse%20Professional%202014/WorkSpace/rmTest/lib/logback-classic-1.0.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: Found binding in [jar:file:/E:/MyEclipse%20Professional%202014/WorkSpace/rmTest/lib/slf4j-jdk14-1.7.12.jar!/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

orderConsumer Started.

TicketInfo@2eae85ab
TicketInfo@70f88a49

7260 [main] INFO  backtype.storm.zookeeper - Starting inprocess zookeeper at port 2000 and dir C:UserscaiexAppDataLocalTemp2a0120cb-5566-4af3-b7e5-64de6a3eb532

7361 [main]******************************************

7368 [main] INFO  backtype.storm.daemon.nimbus - Using default scheduler

7422 [main] INFO  org.apache.curator.framework.imps.CuratorFrameworkImpl - Starting

7578 [main-EventThread] INFO  org.apache.curator.framework.state.ConnectionStateManager - State change: CONNECTED

7578 [ConnectionStateManager-0] WARN  org.apache.curator.framework.state.ConnectionStateManager - There are no ConnectionStateListeners registered.

7581 [main-EventThread] INFO  backtype.storm.zookeeper - Zookeeper state update: :connected:none

8824 [main] INFO  org.apache.curator.framework.imps.CuratorFrameworkImpl - Starting

8885 [main-EventThread] INFO  org.apache.curator.framework.state.ConnectionStateManager - State change: CONNECTED

8885 [ConnectionStateManager-0] WARN  org.apache.curator.framework.state.ConnectionStateManager - There are no ConnectionStateListeners registered.

9113 [main] INFO  org.apache.curator.framework.imps.CuratorFrameworkImpl - Starting

9170 [main-EventThread] INFO  org.apache.curator.framework.state.ConnectionStateManager - State change: CONNECTED

9170 [ConnectionStateManager-0] WARN  org.apache.curator.framework.state.ConnectionStateManager - There are no ConnectionStateListeners registered.

9170 [main-EventThread] INFO  backtype.storm.zookeeper - Zookeeper state update: :connected:none

9211 [main] INFO  org.apache.curator.framework.imps.CuratorFrameworkImpl - Starting

9215 [main] INFO  org.apache.curator.framework.imps.CuratorFrameworkImpl - Starting

9343 [main-EventThread] INFO  org.apache.curator.framework.state.ConnectionStateManager - State change: CONNECTED

9343 [ConnectionStateManager-0] WARN  org.apache.curator.framework.state.ConnectionStateManager - There are no ConnectionStateListeners registered.

9354 [main*******************

9367 [main] INFO  org.apache.curator.framework.imps.CuratorFrameworkImpl - Starting

9426 [main-EventThread] INFO  org.apache.curator.framework.state.ConnectionStateManager - State change: CONNECTED

9426 [ConnectionStateManager-0] WARN  org.apache.curator.framework.state.ConnectionStateManager - There are no ConnectionStateListeners registered.

9426 [main-EventThread] INFO  backtype.storm.zookeeper - Zookeeper state update: :connected:none

9460 [main] INFO  org.apache.curator.framework.imps.CuratorFrameworkImpl - Starting

9493 [main-EventThread] INFO  org.apache.curator.framework.state.ConnectionStateManager - State change: CONNECTED

9493 [ConnectionStateManager-0] WARN  org.apache.curator.framework.state.ConnectionStateManager - There are no ConnectionStateListeners registered.

9562 [main] INFO  backtype.storm.daemon.supervisor - Starting supervisor with id cb0255e3-3fba-439f-b485-02accfb17fed at host caiex-oltp2

9568 [main] *************************

9575 [main] INFO  org.apache.curator.framework.imps.CuratorFrameworkImpl - Starting

9626 [main-EventThread] INFO  org.apache.curator.framework.state.ConnectionStateManager - State change: CONNECTED

9626 [ConnectionStateManager-0] WARN  org.apache.curator.framework.state.ConnectionStateManager - There are no ConnectionStateListeners registered.

9627 [main-EventThread] INFO  backtype.storm.zookeeper - Zookeeper state update: :connected:none

9660 [main] INFO  org.apache.curator.framework.imps.CuratorFrameworkImpl - Starting

9693 [main-EventThread] INFO  org.apache.curator.framework.state.ConnectionStateManager - State change: CONNECTED

9693 [ConnectionStateManager-0] WARN  org.apache.curator.framework.state.ConnectionStateManager - There are no ConnectionStateListeners registered.

********************

TicketInfo@2eae85ab
TicketInfo@70f88a49

Bolt-1 : 28
Bolt-2 : 1
Bolt-1 : 28
Bolt-2 : 3
Bolt-1 : 18
Bolt-2 : 1
Bolt-1 : 15
Bolt-2 : 6
Bolt-1 : 23
Bolt-2 : 2
Bolt-1 : 18
Bolt-2 : 2

TicketInfo@4bd0a952

19543 [timer] INFO  backtype.storm.daemon.nimbus - Setting new assignment for topology id position-1-1428982465: #backtype.storm.daemon.common.Assignment{:master-code-dir "C:\Users\caiex\AppData\Local\Temp\9c04c562-c065-4bc9-a1e6-3200fdd66acb\nimbus\stormdist\position-1-1428982465", :node->host {"cb0255e3-3fba-439f-b485-02accfb17fed" "caiex-oltp2"}, :executor->node+port {[3 3] ["cb0255e3-3fba-439f-b485-02accfb17fed" 1024], [4 4] ["cb0255e3-3fba-439f-b485-02accfb17fed" 1024], [2 2] ["cb0255e3-3fba-439f-b485-02accfb17fed" 1024], [1 1] ["cb0255e3-3fba-439f-b485-02accfb17fed" 1024]}, :executor->start-time-secs {[4 4] 1428982474, [1 1] 1428982474, [2 2] 1428982474, [3 3] 1428982474}}

TicketInfo@27d21cf5
TicketInfo@353e5206
TicketInfo@687eecff
TicketInfo@bf6d6ca
TicketInfo@3b757fe1

Answer 1

嗯，我是在接收的本地队列中让线程睡2s，这样确实可以稳定运行，但是对性能伤害太大了

Answer 2

最后是如何解决的还记得不？我也遇到这样的问题了

Answer 3

同问， 我这问题和楼主一样啊，最开始正常工作，过一段时间后只有spout发 bolt就不跑了。  尝试过在spout里加了1ms的延时，能够正常运行很长时间，不过还是会出现同样的情况。