I just found that too. Seems it's becuse 0.9.1 usses netty by default instead of zeromq ( guess thats why it was working with 0.8.1). Presently looking for the configuration parameter by which i can tell it to use zmq instead of netty. Let me know if you have any clue. Otherwise i just have to chuck the 0.9.1 and get back to 0.8.1
On 10 July 2014 17:02, Harsha <st...@harsha.io> wrote: > Hi Suparno, > It might be because of > https://issues.apache.org/jira/browse/STORM-187. Can you try using > 0.9.2-incubating release. > -Harsha > > > On Thu, Jul 10, 2014, at 07:38 AM, Suparno Datta wrote: > > Hi, > > I am using storm 0.9.1-incubating on a single machine cluster to run a > simple twitter hashtag extractor. I am using the Storm-twitter-workshop > which i found to be extremely useful. > > https://github.com/kantega/storm-twitter-workshop > > I have used this program before with storm 0.8.1 and it ran like a charm. > I might mention that was on a server machine with quite 2 quad xeon > processors. > > This time i am trying it on my laptop( i5 , 8GB). But i am constantly > getting this error in the worker log files > > 2014-07-10 13:01:47 b.s.m.n.Client [INFO] Reconnect ... [24] > 2014-07-10 13:01:58 b.s.m.n.Client [INFO] Reconnect ... [25] > 2014-07-10 13:02:09 b.s.m.n.Client [INFO] Reconnect ... [26] > 2014-07-10 13:02:19 STDIO [ERROR] Jul 10, 2014 1:02:19 PM > org.jboss.netty.channel.DefaultChannelPipeline > WARNING: An exception was thrown by a user handler while handling an > exception event ([id: 0x563f7062] EXCEPTION: java.net.ConnectException: > connection timed out) > java.lang.IllegalArgumentException: timeout value is negative > at java.lang.Thread.sleep(Native Method) > at backtype.storm.messaging.netty.Client.reconnect(Client.java:94) > at > backtype.storm.messaging.netty.StormClientHandler.exceptionCaught(StormClientHandler.java:118) > at > org.jboss.netty.handler.codec.frame.FrameDecoder.exceptionCaught(FrameDecoder.java:377) > at org.jboss.netty.channel.Channels.fireExceptionCaught(Channels.java:525) > at > org.jboss.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:140) > at > org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:82) > at > org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) > at > org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:41) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > > > Now here comes the stranges part. If i declare just one instance of the > hashtag extractor Bolt it fails to get anything but for more that 1 it does > manage to get me a few hashtags though with quite high latency. Another > strange part related to this machine is if i declare more than 2 > supervisor.slots.ports the program doesnt even launch any more showing some > initialitzation error. > > Sorry if i blabbered a lot about the hardware and stuff. But somehow to me > it seemed quite related to the problem. Any sort of help will be really > useful. > > Thanks, > > Suparno > > > > -- Suparno Datta
