Hi,

We are using Storm 0.9.3. We have a topology running a Shell bolt that
launches a Python process. After running for 3-4 hours, we saw this
exception on one of the worker nodes:

2015-03-09T11:08:50.009-0500 b.s.util [ERROR] Async loop died!
java.lang.RuntimeException: java.lang.NullPointerException
  at
backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:128)
~[storm-core-0.9.3.jar:0.9.3]
  at
backtype.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:99)
~[storm-core-0.9.3.jar:0.9.3]
  at
backtype.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:80)
~[storm-core-0.9.3.jar:0.9.3]
  at
backtype.storm.disruptor$consume_loop_STAR_$fn__1460.invoke(disruptor.clj:94)
~[storm-core-0.9.3.jar:0.9.3]
  at backtype.storm.util$async_loop$fn__464.invoke(util.clj:463)
~[storm-core-0.9.3.jar:0.9.3]
  at clojure.lang.AFn.run(AFn.java:24) [clojure-1.5.1.jar:na]
  at java.lang.Thread.run(Thread.java:745) [na:1.7.0_67]
Caused by: java.lang.NullPointerException: null
  at clojure.lang.RT.intCast(RT.java:1087) ~[clojure-1.5.1.jar:na]
  at
backtype.storm.daemon.worker$mk_transfer_fn$fn__3549.invoke(worker.clj:129)
~[storm-core-0.9.3.jar:0.9.3]
  at
backtype.storm.daemon.executor$start_batch_transfer__GT_worker_handler_BANG_$fn__3283.invoke(executor.clj:258)
~[storm-core-0.9.3.jar:0.9.3]
  at
backtype.storm.disruptor$clojure_handler$reify__1447.onEvent(disruptor.clj:58)
~[storm-core-0.9.3.jar:0.9.3]
  at
backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:125)
~[storm-core-0.9.3.jar:0.9.3]
  ... 6 common frames omitted

Looking at few other mail threads with similar exception, it appears this
is a known issue with using Shell bolts. Can someone please confirm if this
is the case, and is there any fix / workaround for the problem.

Thanks
Hemanth

Reply via email to