Damn it, got network timeout. CPU 3 is using 100% cpu from memcached. Here is the result of stat to verify using new version of memcached and libevent:
STAT version 1.4.19 STAT libevent 2.0.18-stable On Saturday, May 3, 2014 11:55:31 PM UTC-7, [email protected] wrote: > > Just upgraded all 5 web-servers to memcached 1.4.19 with libevent 2.0.18. > Will advise if I see memcached timeouts. Should be good though. > > Thanks so much for all the help and patience. Really appreciated. > > On Friday, May 2, 2014 10:20:26 PM UTC-7, [email protected] wrote: >> >> Updates: >> Status: Invalid >> >> Comment #20 on issue 363 by [email protected]: MemcachePool::get(): >> Server >> 127.0.0.1 (tcp 11211, udp 0) failed with: Network timeout >> http://code.google.com/p/memcached/issues/detail?id=363 >> >> Any repeat crashes? I'm going to close this. it looks like remi >> shipped .19. reopen or open a new one if it hangs in the same way >> somehow... >> >> Well. 19 won't be printing anything, and it won't hang, but if it's >> actually our bug and not libevent it would end up spinning CPU. Keep an >> eye >> out I guess. >> >> -- >> You received this message because this project is configured to send all >> >> issue notifications to this address. >> You may adjust your notification preferences at: >> https://code.google.com/hosting/settings >> > -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
