This is my netty config, perhaps this will help? Swap yours for this, does the problem persist? Introduce your preferred values in a binary search pattern to track down the problem configuration item. Hopefully that specified below will get your topology working again..
storm.messaging.transport: "backtype.storm.messaging.netty.Context" storm.messaging.netty.buffer_size: 16384 storm.messaging.netty.max_retries: 10 storm.messaging.netty.min_wait_ms: 1000 storm.messaging.netty.max_wait_ms: 5000 D From: Binita Bharati<mailto:binita.bhar...@gmail.com> Sent: ?Wednesday?, ?2? ?April? ?2014 ?08?:?18 To: user@storm.incubator.apache.org<mailto:user@storm.incubator.apache.org> The same issue is still observed in worker logs. Anyone has any other inputs ? Thanks On Tue, Apr 1, 2014 at 8:25 AM, Binita Bharati <binita.bhar...@gmail.com> wrote: > Thanks , will give it a shot.. > > On Fri, Mar 28, 2014 at 9:27 AM, bijoy deb <bijoy.comput...@gmail.com> wrote: >> Hi, >> >> Try modifying "storm.messaging.netty.max_retries: 100" to a lower >> value,e.g. "storm.messaging.netty.max_retries: 10". >> >> Thanks >> Bijoy >> >> >> On Fri, Mar 28, 2014 at 8:48 AM, Binita Bharati <binita.bhar...@gmail.com> >> wrote: >>> >>> Hi all, >>> >>> Am using storm-0.9.0.1. >>> >>> The following error is seen in the worker logs: >>> >>> 2014-03-25 16:18:24 STDIO [ERROR] Mar 25, 2014 4:18:24 PM >>> org.jboss.netty.channel.DefaultChannelPipeline >>> WARNING: An exception was thrown by a user handler while handling an >>> exception event ([id: 0x8068e4b0] EXCEPTION: >>> java.net.ConnectException: Connection refused) >>> java.lang.IllegalArgumentException: timeout value is negative >>> at java.lang.Thread.sleep(Native Method) >>> at backtype.storm.messaging.netty.Client.reconnect(Client.java:78) >>> at >>> backtype.storm.messaging.netty.StormClientHandler.exceptionCaught(StormClientHandler.java:108) >>> 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.processSelectedKeys(NioClientBoss.java:109) >>> at >>> org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:78) >>> 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$Worker.runTask(ThreadPoolExecutor.java:886) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >>> at java.lang.Thread.run(Thread.java:662) >>> >>> >>> Relevant Netty config from 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: 100 >>> storm.messaging.netty.max_wait_ms: 1000 >>> storm.messaging.netty.min_wait_ms: 100 >>> >>> Anyone knows why ? >>> >>> Thanks >>> Binita >> >>
