Re: High Slave CPU Intermittently After Replication

On 11/26/2012 2:41 PM, richardg wrote: We started having high load again today a few times today, each time looking at SPM monitor our filter cache starts having high lookups and low hit rate, this is our filtercache setting: would it be possibly too slow? here is the graph when it happens:

Re: High Slave CPU Intermittently After Replication

We started having high load again today a few times today, each time looking at SPM monitor our filter cache starts having high lookups and low hit rate, this is our filtercache setting: would it be possibly too slow? here is the graph when it happens:

Re: High Slave CPU Intermittently After Replication

Re: High Slave CPU Intermittently After Replication

that's very strange. How much memory are you giving the JVM? And how much memory is on your machine? If your index is cutting in half on optimize, then it sounds like you're re-indexing everything. Optimize will squeeze out all the data left around by document deletes or updates, so the only reaso

Re: High Slave CPU Intermittently After Replication

We tried using MergeFactor setting but out CPU Load/Slow Query time issues were more widespread, optimizing the index always alleviated the issue that is why we are using it now. Our index is 2 GB when optimized and would balloon to over 4 GB so we thought the issue was it was getting too big. I

Re: High Slave CPU Intermittently After Replication

One question is, why optimise? The newer TieredMergePolicy, as I understand it, takes away much of the need for optimising an index. As to maxing, after a replication, your caches need warming. Watch how often you replicate, nd check on the admin UI how long it takes to warm caches. You may be max