Comment #1 on issue 366 by [email protected]: Memcached 1.4.19 takes 100%
CPU
http://code.google.com/p/memcached/issues/detail?id=366
Could you attack gdb to a stuck process and get a backtrace?
gdb -p $(pidof memcached)
thread apply all bt
Are you getting timeouts or or it just spinning cpu?
Can you provide:
- Exact kernel version (uname -a)
- How memcached was built (source? yum repo? which repo?)
- Output of: "stats", "stats settings", "stats conns"
- Output of: lsof -p $(pidof memcached)
- The above gdb backtrace
We had one other report of this but the user was also seeing it under .18.
Are you sure it never happens there?
How long does it take between starting it and when it craps out?
Thank you
--
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.
