Hi,

One of my bolts and my spout periodically cause the following exception

java.lang.RuntimeException: java.net.UnknownHostException:
Mint15-Vostro-410: Mint15-Vostro-410
        at 
backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:90)
        at 
backtype.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:61)
        at 
backtype.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:62)
        at 
backtype.storm.daemon.executor$fn__3498$fn__3510$fn__3557.invoke(executor.clj:730)
        at backtype.storm.util$async_loop$fn__444.invoke(util.clj:403)
        at clojure.lang.AFn.run(AFn.java:24)
        at java.lang.Thread.run(Thread.java:662)
Caused by: java.net.UnknownHostException: Mint15-Vostro-410: Mint15-Vostro-410
        at java.net.InetAddress.getLocalHost(InetAddress.java:1402)
        at backtype.storm.daemon.executor$metrics_tick.invoke(executor.clj:264)
        at 
backtype.storm.daemon.executor$fn__3498$tuple_action_fn__3500.invoke(executor.clj:604)
        at 
backtype.storm.daemon.executor$mk_task_receiver$fn__3421.invoke(executor.clj:386)
        at 
backtype.storm.disruptor$clojure_handler$reify__2962.onEvent(disruptor.clj:43)
        at 
backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:87)
        ... 6 more

*cat /etc/hosts*
127.0.0.1 localhost
127.0.1.1 Mint15-Vostro-410

*storm.yaml*
*storm.messaging.transport: "backtype.storm.messaging.netty.Context"*
*storm.messaging.netty.server_worker_threads: 1*
*storm.messaging.netty.client_worker_threads: 1*
*storm.messaging.netty.buffer_size: 5242880*
*storm.messaging.netty.max_retries: 10*
*storm.messaging.netty.max_wait_ms: 1000*
*storm.messaging.netty.min_wait_ms: 100*


The topology works OK but the workers seem to get restarted during the
execution. Not clear whether it is related to the exception above or not.

Any idea?

Thanks

Julien

-- 

Open Source Solutions for Text Engineering

http://digitalpebble.blogspot.com/
http://www.digitalpebble.com
http://twitter.com/digitalpebble

Reply via email to