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 reason I can imagine that your index drops by 50% if if you've replaced every document that was there originally. And I'd also guess that you don't have enough activity to trigger merges often enough to squeeze out the deleted documents' data. But this sounds ever so much like you're running with not much memory and are getting into heavy swapping or something like that s your index crosses some threshold. But that's just a guess. Best Erick On Fri, Nov 16, 2012 at 10:23 AM, richardg <richa...@dvdempire.com> wrote: > 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 notice a small spike in CPU load after every replication but then after a > couple of seconds load returns to normal (which is less that 25%) it is > just > sometimes (once in the last week) that it would spike and stay high (10 > minutes) until I optimized the index. Before I would optimize the index > after every commit the issue would occur more often. > > We would like to not optimize and use the built in Merging but we had > before > and the issue would occur more often. We were thinking of trying a > mergefactor of 2 again but I'm afraid this issues will return. > > I installed SPM and am monitoring it to see if it tells me anything, I can > post the results on Monday and hopefully it will tell us something. > > At this time we aren't warming and caches, we weren't sure if this was an > issue because our slowdowns weren't happening every time. Also, we are > using > the join functionality of Solr 4 if that helps. > > Thanks for your help > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/High-Slave-CPU-Intermittently-After-Replication-tp4020520p4020743.html > Sent from the Solr - User mailing list archive at Nabble.com. >
