Hi. Seems like these are logs which occurs in progress of connecting. (We may want to lower its log level cause it doesn't mean we give up to connect, just attempting.)
Your worker should print either "Giving up to connect to ", or "connection established to ". Former means that worker gave up connecting to other worker, and that worker kills itself. If you received this log, you may want to check that these are able to connect each other. Latter means worker succeed to connect other worker, so it is safe. Hope this helps. Thanks, Jungtaek Lim (HeartSaVioR) 2015-07-02 8:59 GMT+09:00 张炜 <[email protected]>: > Hi all, > I met strange problems and below are some typical log output. > Could you please help me know where the problem is? Or could anyone guide > me which areas that I can start to investigate and where to find related > materials? > > These things look very internal to me that I don't know where to start. > Thank you very much! > > Regards, > Sai > > 2015-07-01T01:42:53.290+0000 b.s.d.executor [INFO] Shutting down executor > mycheck:[97 97] > 2015-07-01T01:42:53.290+0000 b.s.util [INFO] Async loop interrupted! > 2015-07-01T01:42:53.291+0000 b.s.util [INFO] Async loop interrupted! > 2015-07-01T01:42:53.291+0000 b.s.d.executor [INFO] Shut down executor > mycheck:[97 97] > > > 2015-07-01T01:42:52.868+0000 b.s.m.n.Client [INFO] connection attempt 1 to > Netty-Client-localhost/127.0.0.1:6702 scheduled to run in 0 ms > 2015-07-01T01:42:52.875+0000 b.s.m.n.Client [INFO] connection established to > Netty-Client-localhost/127.0.0.1:6702 > 2015-07-01T01:42:52.889+0000 b.s.m.loader [INFO] Shutting down > receiving-thread: [Topology-2-1435680709, 6702] > 2015-07-01T01:42:52.891+0000 b.s.m.n.Client [INFO] closing Netty Client > Netty-Client-localhost/127.0.0.1:6702 > 2015-07-01T01:42:52.891+0000 b.s.m.n.Client [INFO] waiting up to 600000 ms to > send 1 pending messages to Netty-Client-localhost/127.0.0.1:6702 > 2015-07-01T15:49:30.089+0000 o.a.s.c.r.ExponentialBackoffRetry [WARN] > maxRetries too large (300). Pinning to 29 > 2015-07-01T15:49:30.132+0000 o.a.s.c.r.ExponentialBackoffRetry [WARN] > maxRetries too large (300). Pinning to 29 > 2015-07-01T15:49:30.148+0000 o.a.s.c.r.ExponentialBackoffRetry [WARN] > maxRetries too large (300). Pinning to 29 > 2015-07-01T15:49:30.150+0000 o.a.s.c.r.ExponentialBackoffRetry [WARN] > maxRetries too large (300). Pinning to 29 > 2015-07-01T15:49:30.151+0000 o.a.s.c.r.ExponentialBackoffRetry [WARN] > maxRetries too large (300). Pinning to 29 > 2015-07-01T15:49:30.268+0000 b.s.m.n.Client [ERROR] connection attempt 1 to > Netty-Client- failed: java.lang.RuntimeException: Returned channel was > actually not established > 2015-07-01T15:49:30.291+0000 b.s.m.n.Client [ERROR] connection attempt 1 to > Netty-Client-6703 failed: java.lang.RuntimeException: Returned channel was > actually not established > 2015-07-01T15:49:30.379+0000 b.s.m.n.Client [ERROR] connection attempt 2 to > Netty-Client- failed: java.lang.RuntimeException: Returned channel was > actually not established > 2015-07-01T15:49:30.886+0000 b.s.m.n.Client [ERROR] connection attempt 2 to > Netty-Client-/15.50.46.234:6703 failed: java.lang.RuntimeException: Returned > channel was actually not established > 2015-07-01T15:49:30.912+0000 b.s.m.n.Client [ERROR] connection attempt 3 to > Netty-Client-:6702 failed: java.lang.RuntimeException: Returned channel was > actually not established > 2015-07-01T15:49:31.010+0000 b.s.m.n.Client [ERROR] connection attempt 3 to > Netty-Client-:6703 failed: java.lang.RuntimeException: Returned channel was > actually not established > 2015-07-01T15:49:31.047+0000 b.s.m.n.Client [ERROR] connection attempt 4 to > Netty-Client-:6702 failed: java.lang.RuntimeException: Returned channel was > actually not established > > -- Name : 임 정택 Blog : http://www.heartsavior.net / http://dev.heartsavior.net Twitter : http://twitter.com/heartsavior LinkedIn : http://www.linkedin.com/in/heartsavior
