Our current search is faceting on a single integer field. The field is
multi-valued.
facet=true
facet.mincount=1
facet.limit=-1
facet.field=fieldA
The number of unique values in our index for fieldA is around 8000, and a
typical query can return about 500 counts. A typical single document can
We recently created a custom class for our spellchecking implementation in
Solr. We decided to include the class in a custom jar and deployed it to
the /lib directory in solr_home to use it as a plugin.
After a while (about 12 hours), the heap usage for Solr slowly starts to
rise, and we
consuming with time? How large of a heap are you using, is
Solr the only webapp in your TOmcat, and are you using sorting or
faceting?
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: CameronL cameron.develo...@gmail.com
To: solr-user
I've searched through the forums and seen a few similar problems to this, but
nothing that seemed to help much.
We're running Solr 1.3 on Tomcat 6.0.16 and Java 6. We've been having
performance problems with our search, causing long query times under normal
traffic. We've taken a thread dump
Unfortunately upgrading to 1.4 isn't an option for us at the moment.
Since we're stuck using 1.3, is there anything in particular we need to do
to prevent these threads from locking (through configuration or something)
or is this sort of expected/unavoidable using 1.3?
Yonik Seeley-2 wrote:
what you are replying to since you removed the
original email (sounds like somebody suggested using bq).
I think it might help if you send the actual URL you are using.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
From: CameronL
So the bq parameter works with the standard request handler (I don't have to
specify defType=dismax)??
I've been running a few tests and it doesn't seem to be picking up the bq.
I've boosted one of the values very high (like 1000) compared to the other
fields and it doesn't seem to be affecting
I'm trying to create the boost query (bq parameter) effect with the standard
request handler. Unfortunately, going to the dismax handler isn't really an
option for me, so I'm trying to create a similar effect.
I have an integer field, 'searchTier', that sort of needs to be factored
into every
What is the current strategy for doing distributed search for Solr? We
currently have our index divided over 3 servers:
solr1
solr2
solr3
In order to balance the load, our application calls each with a 'shards'
parameter to get the data:
solr1:8080/select?shards=solr1,solr2,solr3...
Yonik Seeley wrote:
On Thu, Aug 7, 2008 at 7:32 PM, CameronL [EMAIL PROTECTED]
wrote:
What is the current strategy for doing distributed search for Solr? We
currently have our index divided over 3 servers:
solr1
solr2
solr3
In order to balance the load, our application calls each
probably do the trick, huh?
Erik
On Jul 31, 2008, at 7:34 PM, CameronL wrote:
My problem is a little complex, so please bear with me.
I currently have a set of documents that need to be tiered, and
depending
on what tier they are in, a configurable boost should be applied
The dataDir parameter specified in the core... element in multicore.xml
does not seem to point to the correct directory. I commented out the
dataDir element from solrconfig.xml in all of my cores.
I could explicitly set the dataDir for each core in all of the
solrconfig.xml files, but I would
My problem is a little complex, so please bear with me.
I currently have a set of documents that need to be tiered, and depending
on what tier they are in, a configurable boost should be applied,
essentially affecting the score and ordering of the search results.
My first idea was to create 10
13 matches
Mail list logo
