Hi,
I have a Lucene query as following (toString represenation of Lucene's
Query object):
+(topics:29)^2 (topics:38)^3 +(-id:41135)
It works fine when I am using it as a lucene query in
SolrIndexSearcher.getDocList function.
However, now I want to use it as a Solr query and query against a
coll
Anything else regarding gc tuning.
On Mon, 20 Jan, 2020, 8:08 AM Rajdeep Sahoo,
wrote:
> Initially we were getting the warning message as ulimit is low i.e. 1024
> so we changed it to 65000
> Using ulimit -u 65000.
>
> Then the error was failed to reserve shared memory error =1
> Because of th
Initially we were getting the warning message as ulimit is low i.e. 1024
so we changed it to 65000
Using ulimit -u 65000.
Then the error was failed to reserve shared memory error =1
Because of this we removed
-xx : +uselargepages
Now in console log it is showing
Could not find or load main c
I had a similar issue with a large number of facets. There is no way (At
least I know) your can get an acceptable response time from search engine
with high number of facets.
The way we solved the issue was to cache shallow Facets data structure in
the web services. Facts structures are refreshed
Initially we were getting the warning message as ulimit is low i.e. 1024
so we changed it to 65000
Using ulimit -u 65000.
Then the error was failed to reserve shared memory error =1
Because of this we removed
-xx : +uselargepages
Now in console log it is showing
Could not find or load main c
What message do you get that means the heap space is full?
Java will always use all of the heap, either as live data or not-yet-collected
garbage.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jan 19, 2020, at 5:47 PM, Rajdeep Sahoo wrote:
>
> H
Hi,
Currently there is no request or indexing is happening.
It's just start up
And during that time heap is getting full.
Index size is approx 1 g.
On Mon, 20 Jan, 2020, 7:01 AM Walter Underwood,
wrote:
> A new garbage collector won’t fix it, but it might help a bit.
>
> Requesting 200 fac
A new garbage collector won’t fix it, but it might help a bit.
Requesting 200 facet fields and having 50-60 of them with results is a huge
amount of work for Solr. A typical faceting implementation might have three to
five facets. Your requests will be at least 10X to 20X slower.
Check the CPU
Hi,
Still facing the same issue...
Anything else that we need to check.
On Mon, 20 Jan, 2020, 4:07 AM Walter Underwood,
wrote:
> With Java 1.8, I would use the G1 garbage collector. We’ve been running
> that combination in prod for three years with no problems.
>
> SOLR_HEAP=8g
> # Use G1 GC -
With Java 1.8, I would use the G1 garbage collector. We’ve been running that
combination in prod for three years with no problems.
SOLR_HEAP=8g
# Use G1 GC -- wunder 2017-01-23
# Settings from https://wiki.apache.org/solr/ShawnHeisey
GC_TUNE=" \
-XX:+UseG1GC \
-XX:+ParallelRefProcEnabled \
-XX:G
I think so as the ConnectionImpl in solr is not in line with the description of
the java connection interface
> Op 19 jan. 2020 om 21:23 heeft Erick Erickson het
> volgende geschreven:
>
> Is this a Solr issue?
>
>> On Sun, Jan 19, 2020, 14:24 Nick Vercammen
>> wrote:
>>
>> Hello,
>>
>> I
Is this a Solr issue?
On Sun, Jan 19, 2020, 14:24 Nick Vercammen
wrote:
> Hello,
>
> I'm trying to write a solr driver for metabase. Internally metabase uses a
> C3P0 connection pool. Upon checkout of the connection from the pool the
> library does a call to isValid(0) (timeout = 0)
>
> Accordin
Hello,
I'm trying to write a solr driver for metabase. Internally metabase uses a
C3P0 connection pool. Upon checkout of the connection from the pool the
library does a call to isValid(0) (timeout = 0)
According to the javadocs (
https://docs.oracle.com/en/java/javase/11/docs/api/java.sql/java/sq
Please reply anyone
On Sun, 19 Jan, 2020, 10:55 PM Rajdeep Sahoo,
wrote:
> We are using solr 7.7 . Ram size is 24 gb and allocated space is 12 gb. We
> have completed indexing after starting the server suddenly heap space is
> getting full.
>Added gc params , still not working and jdk versi
We are using solr 7.7 . Ram size is 24 gb and allocated space is 12 gb. We
have completed indexing after starting the server suddenly heap space is
getting full.
Added gc params , still not working and jdk version is 1.8 .
Please find the below gc params
-XX:NewRatio=2
-XX:SurvivorRatio=3
-XX:
15 matches
Mail list logo