I am seeing a lot of failures in the storm UI. I set up a task hook with
a stack trace so that I could see what was causing the failures and I get
the following stack trace in my logs:
2015-02-17 22:58:13 InfoLoggerTaskHook [INFO] component parse,taskId 27,
failLatencyMs null, stack java.lang.Throwable
at InfoLoggerTaskHook.spoutFail(InfoLoggerTaskHook.java:29)
at
backtype.storm.daemon.executor$fail_spout_msg.invoke(executor.clj:355)
at
backtype.storm.daemon.executor$fn$reify__3442.expire(executor.clj:414)
at backtype.storm.utils.RotatingMap.rotate(RotatingMap.java:56)
at
backtype.storm.daemon.executor$fn__3439$tuple_action_fn__3445.invoke(executor.clj:419)
at
backtype.storm.daemon.executor$mk_task_receiver$fn__3430.invoke(executor.clj:386)
at
backtype.storm.disruptor$clojure_handler$reify__2971.onEvent(disruptor.clj:43)
at
backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:87)
at
backtype.storm.utils.DisruptorQueue.consumeBatch(DisruptorQueue.java:49)
at backtype.storm.disruptor$consume_batch.invoke(disruptor.clj:59)
at
backtype.storm.daemon.executor$fn__3439$fn__3454$fn__3483.invoke(executor.clj:524)
at backtype.storm.util$async_loop$fn__453.invoke(util.clj:429)
at clojure.lang.AFn.run(AFn.java:24)
at java.lang.Thread.run(Thread.java:745)
Is there anything that I can do to prevent this from happening?
I have TOPOLOGY_ACKERS set to 0 and TOPOLOGY_ENABLE_MESSAGE_TIMEOUTS set to
false. Shouldn't this prevent this from happening?
I am using storm 0.9.0.1
Thanks,
