So what is the issue and the Solution?
Do i need to change any configurations in my solrconfig.xml ?
So I have attached my solrconfig.xml
have a look.
On Wed, Apr 9, 2014 at 1:32 AM, Toke Eskildsen t...@statsbiblioteket.dkwrote:
Shawn Heisey [s...@elyograg.org] wrote:
Are you using the Jetty
I am using apache solr-4.6.1 and solr works fine when the number of
requests are less
*But when the number of concurrent requests are more Solr is not able to
handle it and it gives the following errors on server.*
834246 [qtp1797259051-168] WARN org.eclipse.jetty.servlet.ServletHandler
-
On 4/8/2014 3:17 AM, Sohan Kalsariya wrote:
I am using apache solr-4.6.1 and solr works fine when the number of
requests are less
*But when the number of concurrent requests are more Solr is not able to
handle it and it gives the following errors on server.*
834246 [qtp1797259051-168] WARN
I am using the Jetty that comes with the solr. And I am not using any third
party plugins or patches.
BTW what kinda error is this ?
Is this related to memory issue or what make me understand please.
On Tue, Apr 8, 2014 at 9:25 PM, Shawn Heisey s...@elyograg.org wrote:
On 4/8/2014 3:17 AM,
Shawn Heisey [s...@elyograg.org] wrote:
Are you using the Jetty that comes with Solr, or are you using Jetty
from another source? If you are using Jetty from another source, the
maxThreads parameter may not be high enough. I believe the default in a
typical Jetty config is 200, but the jetty
-Original Message- From: Roman Chyla
Sent: Monday, June 03, 2013 11:53 AM
To: solr-user@lucene.apache.org
Subject: Re: how are you handling killer queries?
I think you should take a look at the TimeLimitingCollector (it is used
also inside SolrIndexSearcher).
My understanding
:
There is the timeAllowed parameter:
http://wiki.apache.org/solr/CommonQueryParameters#timeAllowed
-- Jack Krupansky
-Original Message- From: Roman Chyla
Sent: Monday, June 03, 2013 11:53 AM
To: solr-user@lucene.apache.org
Subject: Re: how are you handling killer queries?
I think you
How are you handling killer queries with solr?
While solr/lucene (currently 4.2.1) is trying to do its best I see sometimes
stupid queries
in my logs, located with extremly long query time.
Example:
q=???+and+??+and+???+and++and+???+and+??
I even get hits for this (hits
On 6/3/2013 2:39 AM, Bernd Fehling wrote:
How are you handling killer queries with solr?
While solr/lucene (currently 4.2.1) is trying to do its best I see sometimes
stupid queries
in my logs, located with extremly long query time.
Example:
q
)?
And the container has no way to simulate a browser stop button in case of a
timeout
to get a sane termination?
Bernd
Am 03.06.2013 16:20, schrieb Shawn Heisey:
On 6/3/2013 2:39 AM, Bernd Fehling wrote:
How are you handling killer queries with solr?
While solr/lucene (currently 4.2.1
On 6/3/2013 8:43 AM, Bernd Fehling wrote:
Hi Shawn,
well, the user is the world and the servers have enough capacity.
So its nothing really to worry about.
OK, could raise timeout from standard 60 to 90, 120 or even 180 seconds.
Just wanted to know how other solr developer handle this.
The
, 2013 4:39 AM
To: solr-user@lucene.apache.org
Subject: how are you handling killer queries?
How are you handling killer queries with solr?
While solr/lucene (currently 4.2.1) is trying to do its best I see sometimes
stupid queries
in my logs, located with extremly long query time.
Example:
q
this?
How are you handling killer queries, just ignoring?
Or something to tune (jetty config about timeout) or filter (query
filtering)?
Would be pleased to hear your comments.
Bernd
There is the timeAllowed parameter:
http://wiki.apache.org/solr/CommonQueryParameters#timeAllowed
-- Jack Krupansky
-Original Message-
From: Roman Chyla
Sent: Monday, June 03, 2013 11:53 AM
To: solr-user@lucene.apache.org
Subject: Re: how are you handling killer queries?
I think you
14 matches
Mail list logo
