I've been experiencing this problem. Running VisualVM on my instances
shows that they spend a lot of time creating WeakReferences
(org.apache.lucene.util.WeakIdentityMap$IdentityWeakReference that is).
I think what's happening here is the heap's not big enough for Lucene's
caches and it ends up thrashing.
You might try bumping up your heap some to see if that helps. It's made
a difference for me, but mostly in delaying the onset and limiting the
occurrence of this. Likely I just need an even larger heap.
Michael
On 12/18/14 17:36, heaven wrote:
Hi,
We have 2 shards, each one has 2 replicas and each Solr instance has a
single thread that constantly uses 100% of CPU:
<http://lucene.472066.n3.nabble.com/file/n4175088/Screenshot_896.png>
After restart it is running normally for some time (approximately until Solr
comes close to Xmx limit), then the mentioned thread start consuming one
CPU. 4 solr instances = minus 4 CPU cores.
We do not commit manually and the search is not used too intensively.
{code}
<autoCommit>
<maxDocs>25000</maxDocs>
<maxTime>300000</maxTime>
<openSearcher>false</openSearcher>
</autoCommit>
<autoSoftCommit>
<maxTime>15000</maxTime>
</autoSoftCommit>
{code}
So I was wondering if that's correct, if this is supposed to be or if
something is wrong with our configuration or with Solr.
Thanks,
Alex
--
View this message in context:
http://lucene.472066.n3.nabble.com/Endless-100-CPU-usage-on-searcherExecutor-thread-tp4175088.html
Sent from the Solr - User mailing list archive at Nabble.com.
