Github user clockfly commented on the pull request:
https://github.com/apache/incubator-storm/pull/103#issuecomment-45414524
@Bobby, I reproduced this. It is random. I will look into this, thanks.
Seems the Netty Client is closed before worker transfer thread is closed.
So, transfer thread got an exception.
137917 [Thread-549-disruptor-worker-transfer-queue] ERROR
backtype.storm.util - Async loop died!
java.lang.RuntimeException: java.lang.RuntimeException: Client is being
closed, and does not take requests any more
at
backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:114)
~[classes/:na]
at
backtype.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:85)
~[classes/:na]
at
backtype.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:78)
~[classes/:na]
at
backtype.storm.disruptor$consume_loop_STAR_$fn__2895.invoke(disruptor.clj:89)
~[classes/:na]
at backtype.storm.util$async_loop$fn__442.invoke(util.clj:434)
~[classes/:na]
at clojure.lang.AFn.run(AFn.java:24) [clojure-1.4.0.jar:na]
at java.lang.Thread.run(Thread.java:679) [na:1.6.0_22]
Caused by: java.lang.RuntimeException: Client is being closed, and does not
take requests any more
at backtype.storm.messaging.netty.Client.send(Client.java:194)
~[classes/:na]
at backtype.storm.utils.TransferDrainer.send(TransferDrainer.java:54)
~[classes/:na]
at
backtype.storm.daemon.worker$mk_transfer_tuples_handler$fn__5765$fn__5766.invoke(worker.clj:322)
~[classes/:na]
at
backtype.storm.daemon.worker$mk_transfer_tuples_handler$fn__5765.invoke(worker.clj:320)
~[classes/:na]
at
backtype.storm.disruptor$clojure_handler$reify__2882.onEvent(disruptor.clj:59)
~[classes/:na]
at
backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:111)
~[classes/:na]
... 6 common frames omitted
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
