no swapping that I'm seeing, although we are noticing a lot higher number of
hard commits than usual.
the config is set up per the NRT suggestions in the docs. autoSoftCommit every
2 seconds and autoCommit every 10 minutes.
there have been 463 updates in the past 2 hours, all followed by hard commits
INFO - 2015-07-20 12:26:20.979; org.apache.solr.update.DirectUpdateHandler2;
start
commit{,optimize=false,openSearcher=true,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false}
INFO - 2015-07-20 12:26:21.021; org.apache.solr.core.SolrDeletionPolicy;
SolrDeletionPolicy.onCommit: commits: num=2
commit{dir=NRTCachingDirectory(org.apache.lucene.store.MMapDirectory@/opt/solr/solr/collection1/data/index
lockFactory=org.apache.lucene.store.NativeFSLockFactory@524b89bd;
maxCacheMB=48.0 maxMergeSizeMB=4.0),segFN=segments_e9nk,generation=665696}
commit{dir=NRTCachingDirectory(org.apache.lucene.store.MMapDirectory@/opt/solr/solr/collection1/data/index
lockFactory=org.apache.lucene.store.NativeFSLockFactory@524b89bd;
maxCacheMB=48.0 maxMergeSizeMB=4.0),segFN=segments_e9nl,generation=665697}
INFO - 2015-07-20 12:26:21.022; org.apache.solr.core.SolrDeletionPolicy;
newest commit generation = 665697
INFO - 2015-07-20 12:26:21.026; org.apache.solr.update.DirectUpdateHandler2;
end_commit_flush
INFO - 2015-07-20 12:26:21.026;
org.apache.solr.update.processor.LogUpdateProcessor; [collection1] webapp=/solr
path=/update params={omitHeader=false&wt=json}
{add=[8653ea29-a327-4a54-9b00-8468241f2d7c (1507244513403338752),
5cf034a9-d93a-4307-a367-02cb21fa8e35 (1507244513404387328),
816e3a04-9d0e-4587-a3ee-9f9e7b0c7d74 (1507244513405435904)],commit=} 0 50
could that be causing some of the problems?
________________________________________
From: Shawn Heisey <apa...@elyograg.org>
Sent: Monday, July 20, 2015 11:44 AM
To: solr-user@lucene.apache.org
Subject: Re: solr blocking and client timeout issue
On 7/20/2015 11:54 AM, Jeremy Ashcraft wrote:
> I'm ugrading to the 1.8 JDK on our dev VM now and testing. Hopefully i
> can get production upgraded tonight.
>
> still getting the big GC pauses this morning, even after applying the
> GC tuning options. Everything was fine throughout the weekend.
>
> My biggest concern is that this instance had been running with no
> issues for almost 2 years, but these GC issues started just last week.
It's very possible that you're simply going to need a larger heap than
you have needed in the past, either because your index has grown, or
because your query patterns have changed and now your queries need more
memory. It could even be both of these.
At your current index size, assuming that there's nothing else on this
machine, you should have enough memory to raise your heap to 5GB.
If there ARE other software pieces on this machine, then the long GC
pauses (along with other performance issues) could be explained by too
much memory allocation out of the 8GB total memory, resulting in
swapping at the OS level.
Thanks,
Shawn
