Hello all,
Lately we have been experiencing an odd issue with our cluster running 3.2.

After about 24 hours we'll see a 10-20% drop in cache hit ratio, which will 
hold steady for several hours before dropping again another 10-20% in what 
looks like stair step.  Eventually, it will drop to almost 0%.

Whats *really* odd is that restarting the cluster temporarily resolves the 
issue, bringing the cache hit ratio back to normal levels for another day or so.

We've added more cache space but that has shown no change in behavior. Memory, 
disk space, and CPU utilization is normal.

The only difference in usage I've identified, is our use cases in which we use 
the Cache API in our plugin have increased.

Any thoughts anyone? Thanks in advance.



Reply via email to