lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Walter Underwood <wunderw...@netflix.com>
Subject Re: Help with relevance failure in Solr 1.3
Date Tue, 14 Apr 2009 18:51:18 GMT
Nope. This is a slave, so no indexing happens, just a sync. The
sync happens once per day. It went bad at a different time.

wunder

On 4/14/09 11:42 AM, "Grant Ingersoll" <gsingers@apache.org> wrote:

> Are there changes occuring when it goes bad that maybe aren't committed?
> 
> On Apr 14, 2009, at 1:59 PM, Walter Underwood wrote:
> 
>> But why would it work for a few days, then go bad and stay bad?
>> 
>> It fails for every multi-term query, even those not in cache.
>> I ran a test with more queries than the cache size.
>> 
>> We do use autowarming.
>> 
>> wunder
>> 
>> On 4/14/09 10:55 AM, "Yonik Seeley" <yonik@lucidimagination.com>
>> wrote:
>> 
>>> On Tue, Apr 14, 2009 at 12:19 PM, Walter Underwood
>>> <wunderwood@netflix.com> wrote:
>>>> The JaroWinkler equals was broken, but I fixed that a month ago.
>>>> 
>>>> Query cache sounds possible, but those are cleared on a commit,
>>>> right?
>>> 
>>> Yes, but if you use autowarming, those items are regenerated and if
>>> there is a problem with equals() then it could re-appear (the cache
>>> items are correct, it's just the lookup that returns the wrong one).
>>> 
>>> -Yonik
>>> http://www.lucidimagination.com
>> 
> 
> --------------------------
> Grant Ingersoll
> http://www.lucidimagination.com/
> 
> Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids)
> using Solr/Lucene:
> http://www.lucidimagination.com/search
> 


Mime
View raw message