Raja, This issue is called the "Hot Key Problem". What happens is that you have "One" or more keys are are very popular and used by all ( or most ) of the code.
For example: We have a key for each singer, one of the keys is "Lady Gaga", the rest are not very interesting ( this is a real example! ). So all of the posts to Gaga keep the server that is "selected" for GaGa Keys active. The Hash is to select one of the servers for each key, it does not: 1) Play FAIR with the distribution of Network packets, 2) Use the same number of connection for all servers. 3) Use the same amount of memory. So the even spread of the keys over the servers needs to be done by a very well selected Key. If you have a "Hot Key" then you see these issues of "Not equal" for memory, cpu, network and connections. The fix is to use a better Key that tends to have a nice spread over the servers. If that is NOT possible, then use more than one "Pool" of Memcache servers as needed to keep these Hot Keys from impacting other keys. Feel free to ask for more help. I have seen this issue and solved it for many projects. -- --- 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 memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
