Are you running these in docker containers?
Also, I’m assuming this is a typo but just in case the setting is Xmx :)
Can you share the OOM stack trace? It’s not always running out of memory,
sometimes Java throws OOM for file handles or threads.
Mike
On Wed, Jan 27, 2021 at 10:00 PM Luke
Shawn,
it's killed by OOME exception. The problem is that I just created empty
collections and the Solr JVM keeps growing and never goes down. there is no
data at all. at the beginning, I set Xxm=6G, then 10G, now 15G, Solr 8.7
always use all of them and it will be killed by oom.sh once jvm usage
On 1/27/2021 5:08 PM, Luke Oak wrote:
I just created a few collections and no data, memory keeps growing but never go
down, until I got OOM and solr is killed
Any reason?
Was Solr killed by the operating system's oom killer or did the death
start with a Java OutOfMemoryError exception?
If
Hi, I am using solr 8.7.0, centos 7, java 8.
I just created a few collections and no data, memory keeps growing but never go
down, until I got OOM and solr is killed
Any reason?
Thanks
Sent from my iPhone
Typically what you would do is add static warming queries to warm all the
caches. These queries are hardcoded into the solrconfig.xml. You'll want to
run the facets you're using in the warming queries particularly facets on
string fields.
Once you add these it will take longer to warm the new
Hi,
A rookie question. We have a Solr cluster that doesn't get too much
traffic. We see that our queries take long time unless we run a script to
send more traffic to Solr.
We are indexing data all the time and use autoCommit.
I am wondering if there is a way to warmup new searcher on commit by
Thanks, I joined the Relevance Slack:
https://opensourceconnections.com/slack, I definitely think a dedicated
Solr workspace would also be good allowing for channels to get involved
with development as well as user based questions.
It does seem like slack has made it increasingly difficult to
Hi,
In Solr 8.6.1, a GET request or a HEAD request for a non-existing term in a
managed resource (stopword or synonym) returns a HTTP status "404 Not
Found".
$ curl -i "
http://localhost:8983/solr/techproducts/schema/analysis/synonyms/english/foobar;
| head -n 1
HTTP/1.1 404 Not Found
$ curl -I
30 Dedicated physical Nodes in the Solr Cloud Cluster, all of identical
configuration
Server01 RHEL 7.x
256GB RAM
10 2TB Spinning Disk in a RAID 10 Configuration (Leaving us 9.8TB usable per
node)
64GB JVM Heap, Tried has high as 100GB, but it appeared that 64GB was faster.
If we set a
Hi,
The boolean query with a bigger value for *rows *times out with the
following message.
The request took too long to iterate over terms. Timeout: timeoutAt
Solr version : Solr 8.6.3
Time allowed : 30
Field :
Query : fl:(term1 OR term2 OR . OR term1)
rows : 1
wt : json/phps
Hi Lucene team,
I have been using Solr 8.4.0 and I encountered an issue where suggest
highlight feature in “BlendedInfixLookupFactory” is not working whenever I
am using “contextField”. While searching online, I came across below page
which does indicate a similar issue but for different
11 matches
Mail list logo