=code500/int/lst
/response
Jeremy D. Branham
Tel: **DOTNET
-Original Message-
From: Jack Krupansky [mailto:j...@basetechnology.com]
Sent: Tuesday, June 03, 2014 6:53 AM
To: solr-user@lucene.apache.org
Subject: Re: suspect SOLR query from D029 (SOLR master)
11 * 11 or 121 query terms
]
Subject: RE: suspect SOLR query from D029 (SOLR master)
These are the typical queries we are using.
I'm curious if any of these parameters could be causing issues when using
synonyms.
?shards=myserver1.com:8080/svc/solr/wdsc,myserver1.com:8080/svc/solr/kmssort=score
descq=(keyword
To: solr-user@lucene.apache.org
Cc: Worley, Chris [HR]
Subject: RE: suspect SOLR query from D029 (SOLR master)
Evidently I didn't understand enough about the synonym filter.
I'm not sure anyone would be able to determine the impact based on the
example queries below.
However I'm curious what
. Branham
Tel: **DOTNET
-Original Message-
From: Branham, Jeremy [HR]
Sent: Friday, May 30, 2014 4:43 PM
To: solr-user@lucene.apache.org
Subject: RE: suspect SOLR query from D029 (SOLR master)
We've switched to CMS GC to see if there is any improvement.
Looking at this use case, G1GC might have
: Monday, June 02, 2014 8:31 PM
To: solr-user@lucene.apache.org
Subject: RE: suspect SOLR query from D029 (SOLR master)
We found a problem with the synonym list, and suspect there was some sort of
recursion causing the memory to be gobbled up until the JVM crashed.
Is this expected behavior from
]; Duncan, Horace W [HR]
Subject: suspect SOLR query from D029 (SOLR master)
Looks like a suspect SOLR query was executed at approx. 8:54am this morning on
the SOLR master server (D029) that caused the java GC to go through the roof.
See below:
2014-05-30 08:54:17,092 ERROR - SolrDispatchFilter
, Jeremy [HR]
Sent: Friday, May 30, 2014 11:52 AM
To: solr-user@lucene.apache.org
Subject: FW: suspect SOLR query from D029 (SOLR master)
We saw the file descriptors peak out and full GCs running causing DOS on our
SOLR servers this morning.
* Does this stack trace give enough information
