So that's the problem. Find out why the workers restart and fix it, maybe timeout, or other errors.
2017-04-27 16:44 GMT+08:00 [email protected] < [email protected]>: > Yes,during that time all the workers were restarted automatically! > > ------------------------------ > Thanks & Regards > > > *From:* Zhechao Ma <[email protected]> > *Date:* 2017-04-27 14:58 > *To:* user <[email protected]> > *Subject:* Re: Re: o.a.s.m.n.StormServerHandler [ERROR] server errors in > handling the request java.io.IOException: Connection reset by peer > check if any worker restart during that time > > 2017-04-27 13:11 GMT+08:00 [email protected] < > [email protected]>: > >> Do you meaning some connections in the zookeeper can't be used? >> >> ------------------------------ >> Thanks & Regards >> >> >> *From:* Dmitry Semenov <[email protected]> >> *Date:* 2017-04-27 12:03 >> *To:* User <[email protected]> >> *Subject:* Re: Re: o.a.s.m.n.StormServerHandler [ERROR] server errors in >> handling the request java.io.IOException: Connection reset by peer >> I run 1.0.3 no issues. Maybe you have a blocking connection in one of >> your spouts or bolts, that result in such crash? >> >> >> On Apr 26, 2017 at 9:00 PM, <[email protected]> wrote: >> >> I have the same problem,and my storm version is 1.0.3. >> >> >> >> *From:* Dmitry Semenov <[email protected]> >> *Date:* 2017-04-27 11:56 >> *To:* User <[email protected]> >> *Subject:* Re: o.a.s.m.n.StormServerHandler [ERROR] server errors in >> handling the request java.io.IOException: Connection reset by peer >> Looks like very old version of storm, which one are you using? >> >> >> On Apr 26, 2017 at 7:37 PM, <马庆祥 <[email protected]>> wrote: >> >> Hello all. >> >> I found a strange error in log file which can cause worker restart. it >> seems to be thrown by storm itself rather my program. >> >> >> >> The error message is: >> >> 2017-04-26 19:14:34.721 o.a.s.m.n.StormServerHandler [ERROR] server errors >> in handling the request >> java.io.IOException: Connection reset by peer >> at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[?:1.7.0_40] >> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) >> ~[?:1.7.0_40] >> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) >> ~[?:1.7.0_40] >> at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[?:1.7.0_40] >> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) >> ~[?:1.7.0_40] >> at >> org.apache.storm.shade.org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:64) >> [storm-core-1.0.2.jar:1.0.2] >> at >> org.apache.storm.shade.org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108) >> [storm-core-1.0.2.jar:1.0.2] >> at >> org.apache.storm.shade.org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318) >> [storm-core-1.0.2.jar:1.0.2] >> at >> org.apache.storm.shade.org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89) >> [storm-core-1.0.2.jar:1.0.2] >> at >> org.apache.storm.shade.org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) >> [storm-core-1.0.2.jar:1.0.2] >> at >> org.apache.storm.shade.org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) >> [storm-core-1.0.2.jar:1.0.2] >> at >> org.apache.storm.shade.org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) >> [storm-core-1.0.2.jar:1.0.2] >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >> [?:1.7.0_40] >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >> [?:1.7.0_40] >> at java.lang.Thread.run(Thread.java:724) [?:1.7.0_40] >> >> >> >> >> And there are mang log as shown below: >> 2017-04-26 19:17:19.516 o.a.s.m.n.Client [INFO] closing Netty Client >> Netty-Client-/X.X.X.X:6720 >> 2017-04-26 19:17:19.518 o.a.s.m.n.Client [INFO] waiting up to 600000 ms >> to send 0 pending messages to Netty-Client-/X.X.X.X:6720 >> 2017-04-26 19:17:19.520 o.a.s.m.n.Client [INFO] closing Netty Client >> Netty-Client-/X.X.X.X:6723 >> 2017-04-26 19:17:19.520 o.a.s.m.n.Client [INFO] waiting up to 600000 ms >> to send 0 pending messages to Netty-Client-/X.X.X.X:6723 >> 2017-04-26 19:17:19.521 o.a.s.m.n.Client [INFO] closing Netty Client >> Netty-Client-/X.X.X.X:6720 >> 2017-04-26 19:17:19.522 o.a.s.m.n.Client [INFO] waiting up to 600000 ms >> to send 0 pending messages to Netty-Client-/X.X.X.X:6720 >> ... ... >> >> >> Thanks & Regards >> Qingxiang Ma >> >> > > > -- > Thanks > Zhechao Ma > > -- Thanks Zhechao Ma
