ERNAL] Re: High cpu usage when adding documents to v7.7 solr cloud
Hi Peter,
This bug was introduced in Solr 7.7.0. It is related to Java 8. And it was
fixed in Solr 7.7.2.
Here are the ways to deal with it:
1. Upgrade to Solr 7.7.2
2. Patch your Solr 7.7
3. Use Java 9+
You can read more on this
Hi Peter,
This bug was introduced in Solr 7.7.0. It is related to Java 8. And it was
fixed in Solr 7.7.2.
Here are the ways to deal with it:
1. Upgrade to Solr 7.7.2
2. Patch your Solr 7.7
3. Use Java 9+
You can read more on this here:
https://issues.apache.org/jira/browse/SOLR-13349
Regards,
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
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
$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
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
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
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
Joel:
I did a little work with SOLR-9296 to try to reduce the number of
objects created, which would relieve GC pressure both at creation and
collection time. I didn't measure CPU utilization before/after, but I
did see up to a 11% increase in throughput.
It wouldn't hurt my feelings at all to ha
Thanks Joel.
2016-11-08 11:43 GMT-08:00 Joel Bernstein :
> It sounds like your scenario, is around 25 queries per second, each pulling
> entire results. This would be enough to drive up CPU usage as you have more
> concurrent requests then CPU's. Since there isn't much IO blocking
> happening, in
It sounds like your scenario, is around 25 queries per second, each pulling
entire results. This would be enough to drive up CPU usage as you have more
concurrent requests then CPU's. Since there isn't much IO blocking
happening, in the scenario you describe, I would expect some pretty busy
CPU's.
Hello:
Any follow up?
2016-11-03 11:18 GMT-07:00 Ray Niu :
> the soft commit is 15 seconds and hard commit is 10 minutes.
>
> 2016-11-03 11:11 GMT-07:00 Erick Erickson :
>
>> Followup question: You say you're indexing 100 docs/second. How often
>> are you _committing_? Either
>> soft commit
>
Followup question: You say you're indexing 100 docs/second. How often
are you _committing_? Either
soft commit
or
hardcommit with openSearcher=true
?
Best,
Erick
On Thu, Nov 3, 2016 at 11:00 AM, Ray Niu wrote:
> Thanks Joel
> here is the information you requested.
> Are you doing heavy writes
the soft commit is 15 seconds and hard commit is 10 minutes.
2016-11-03 11:11 GMT-07:00 Erick Erickson :
> Followup question: You say you're indexing 100 docs/second. How often
> are you _committing_? Either
> soft commit
> or
> hardcommit with openSearcher=true
>
> ?
>
> Best,
> Erick
>
> On Th
Thanks Joel
here is the information you requested.
Are you doing heavy writes at the time?
we are doing write very frequently, but not very heavy, we will update
about 100 solr document per second.
How many concurrent reads are are happening?
the concurrent reads are about 1000-2000 per minute per
Are you doing heavy writes at the time?
How many concurrent reads are are happening?
What version of Solr are you using?
What is the field definition for the double, is it docValues?
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Nov 3, 2016 at 12:56 AM, Ray Niu wrote:
> Hello:
>
ышев
> wrote:
>>
>> I realized what the problem was. One of the Solr threads freezes when
>> importing
>> MP3 files. When there are many such files Solr loads all processors. Is
>> there a
>> way to free thread?
>>
>> Re: High CPU usage after import
the Solr threads freezes when
importing
MP3 files. When there are many such files Solr loads all processors. Is
there a
way to free thread?
Re: High CPU usage after import That could mean that the code is hung
somehow.
Or, maybe Solr is just
working on the commit. Unless you have an explicit commit, t
many such files Solr loads all processors. Is
there a
way to free thread?
Re: High CPU usage after import That could mean that the code is hung
somehow.
Or, maybe Solr is just
working on the commit. Unless you have an explicit commit, the automatic
commit will occur some time after the extract reque
Александр Вандышев
wrote:
> I realized what the problem was. One of the Solr threads freezes when
> importing
> MP3 files. When there are many such files Solr loads all processors. Is
> there a
> way to free thread?
>
> Re: High CPU usage after import That could mean that t
I realized what the problem was. One of the Solr threads freezes when importing
MP3 files. When there are many such files Solr loads all processors. Is there a
way to free thread?
Re: High CPU usage after import That could mean that the code is hung somehow.
Or, maybe Solr is just
working on the
That could mean that the code is hung somehow. Or, maybe Solr is just
working on the commit. Unless you have an explicit commit, the automatic
commit will occur some time after the extract request. How much data are we
talking about?
What does the Solr log say? Compare that to the case where C
Some document types can consume significant CPU resources, such as large PDF
files.
-- Jack Krupansky
-Original Message-
From: Александр Вандышев
Sent: Tuesday, April 1, 2014 9:28 AM
To: Solr User
Subject: High CPU usage after import
I use a update/extract handler for indexing a larg
Hi,
This could be the JVM doing constant GCing because there is not much room in
the
heap for new objects (jstat will help you check this). It could also be that
you have a deadlock - I just saw a similar case with one of our customers' Solr
- out of N CPU cores, one was at 100% and jstack sh
You can try attaching jConsole to the process to see what it shows. If
you're on a *nix box
you can get a gross idea what's going on with "top".
Best
Erick
On Wed, Feb 9, 2011 at 4:31 AM, Erez Zarum wrote:
> Hello,
> We have been running read only solr instances for a few months now,
> yesterda
Hi John,
sounds like this bug in NIO:
http://jira.codehaus.org/browse/JETTY-937
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6403933
I think recent versions of jetty work around this bug, or maybe try
the non-NIO socket connector
Kent
On Tue, Dec 7, 2010 at 9:10 AM, John Russell wrote:
26 matches
Mail list logo
