I know this isn't really the place for this, so please forgive me -
but does this patch look reasonably safe to use to skip the isDeleted
check inside of FunctionQuery?
My reasoning behind this is that many people (us included) will be
building the index on a separate server, and then
It doesn't matter that it's executed on the read-only server... it
matters if any of the docs are marked as deleted. That's the
condition that you probably want to check for.
-Yonik
On Tue, Aug 19, 2008 at 4:26 PM, Matthew Runo [EMAIL PROTECTED] wrote:
I know this isn't really the place for
FYI, I just slipped this optimization into trunk.
-Yonik
On Tue, Aug 19, 2008 at 4:37 PM, Yonik Seeley [EMAIL PROTECTED] wrote:
It doesn't matter that it's executed on the read-only server... it
matters if any of the docs are marked as deleted. That's the
condition that you probably want to
I don't think it will help; for instance SegmentReader of Lucene:
public synchronized Document document(int n, FieldSelector fieldSelector)
Unsynchronized (in future) SOLR caching should help.
-Fuad
I know this isn't really the place for this, so please forgive me - but
does this patch
optimization).
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: Matthew Runo [EMAIL PROTECTED]
To: solr-user@lucene.apache.org
Sent: Tuesday, August 19, 2008 4:26:59 PM
Subject: Re: Deadlock in lucene?
I know this isn't really the place
/ -- Lucene - Solr - Nutch
- Original Message
From: Matthew Runo [EMAIL PROTECTED]
To: solr-user@lucene.apache.org
Sent: Tuesday, August 19, 2008 4:26:59 PM
Subject: Re: Deadlock in lucene?
I know this isn't really the place for this, so please forgive me -
but does this patch look reasonably
Hello folks!
I was just wondering if anyone else has seen this issue under heavy
load. We had some servers set to very high thread limits (12 core
servers with 32 gigs of ram), and found several threads would end up
in this state
Name: http-8080-891
State: BLOCKED on [EMAIL
It's not a deadlock (just a synchronization bottleneck) , but it is a
known issue in Lucene and there has been some progress in improving
the situation.
-Yonik
On Mon, Aug 18, 2008 at 10:55 PM, Matthew Runo [EMAIL PROTECTED] wrote:
Hello folks!
I was just wondering if anyone else has seen
