Re: High CPU usage with Solr 7.7.0

2019-03-29 Thread Erick Erickson
Thanks all. I pushed changes last night, this should be fixed in 7.7.2, 8.1 and master. Meanwhile, this is a trivial change to one line, so two ways to get by would be 1> just make the change yourself locally. Building Solr from scratch is actually not hard. The “ant package” target will get yo

Re: High CPU usage with Solr 7.7.0

2019-03-25 Thread Lukas Weiss
I forward this message. Thanks Adam. Hi, Apologies, I can’t figure out how to reply to the Solr mailing list. I just ran across the same high CPU usage issue. I believe it’’s caused by this commit which was introduced in Solr 7.7.0 https://github.com/apache/lucene-solr/commit/eb652b84edf441d8369

Antwort: Re: Re: High CPU usage with Solr 7.7.0

2019-03-01 Thread Lukas Weiss
$ReferenceHandler.run​(Reference.java:153) Von:"Tomás Fernández Löbbe" An: solr-user@lucene.apache.org, Datum: 27.02.2019 19:34 Betreff: Re: Re: High CPU usage with Solr 7.7.0 Maybe a thread dump would be useful if you still have some instance running on 7.7 On Wed, Feb 27, 2019

Re: Re: High CPU usage with Solr 7.7.0

2019-02-27 Thread Tomás Fernández Löbbe
solr-user@lucene.apache.org, "Lukas Weiss" > , > Datum: 27.02.2019 15:59 > Betreff:Re: High CPU usage with Solr 7.7.0 > > > > Just to add to this. We upgraded to 7.7.0 and saw very large CPU usage > on multi core boxes - sustained in the 1200% range. We

Antwort: Re: High CPU usage with Solr 7.7.0

2019-02-27 Thread Lukas Weiss
I can confirm this. Downgrading to 7.6.0 solved the issue. Thanks for the hint. Von:"Joe Obernberger" An: solr-user@lucene.apache.org, "Lukas Weiss" , Datum: 27.02.2019 15:59 Betreff: Re: High CPU usage with Solr 7.7.0 Just to add to this. We upgra

Re: High CPU usage with Solr 7.7.0

2019-02-27 Thread Joe Obernberger
Just to add to this.  We upgraded to 7.7.0 and saw very large CPU usage on multi core boxes - sustained in the 1200% range.  We then switched to 7.6.0 (no other configuration changes) and the problem went away. We have a 40 node cluster and all 40 nodes had high CPU usage with 3 indexes stored