Thanks Shalin, I'd forgotten about that one
On Thu, Oct 22, 2015 at 11:22 PM, Shalin Shekhar Mangar
wrote:
> I think you running into
> https://issues.apache.org/jira/browse/SOLR-6136 where a spin lock in
> ConcurrentUpdateSolrServer blocks with high cpu usage. Try upgrading
> to 4.10.x but f
I think you running into
https://issues.apache.org/jira/browse/SOLR-6136 where a spin lock in
ConcurrentUpdateSolrServer blocks with high cpu usage. Try upgrading
to 4.10.x but for best results, upgrade to 5.x because of all the
fixes that have been added since and also because no new releases will
Thanks Erick. Currently, migrating to 5.3 and it is taking a bit of
time. Meanwhile, I looked at the JIRAs from the blog and the stack trace
looks a bit different from what I see but not sure if they are related.
Also, as per the stack trace I have included in my original email, it is
the tomca
The details are in Tim's blog post and the linked JIRAs
Unfortunately, the only real solution I know of is to upgrade
to at least Solr 5.2. Meanwhile, throttling the indexing rate
will at least smooth out the issue. Not a great approach but
all there is for 4.6.
Best,
Erick
On Thu, Oct 22, 2015
Erick,
Indexing happening via Solr cloud server. This thread was from the leader. Some
followers show symptom of high cpu during this time. You think this is from
locking? What is the thread that is holding the lock doing? Also, we are unable
to reproduce this issue in load test environment. An
Prior to Solr 5.2, there were several inefficiencies when distributing
updates to replicas, see:
https://lucidworks.com/blog/2015/06/10/indexing-performance-solr-5-2-now-twice-fast/.
The symptom was that there was significantly higher CPU utilization on
the followers
compared to the leader.
The o
