The JaroWinkler equals was broken, but I fixed that a month ago. Query cache sounds possible, but those are cleared on a commit, right?
I could run with a cache size of 0, since our middle tier HTTP cache is leaving almost nothing for the caches to do. I'll try that explain. The stored fields for the "correct" doc are fine, because I can see them when I use a single-term query. The indexed fields seem OK, because that query works. wunder On 4/14/09 9:11 AM, "Yonik Seeley" <yo...@lucidimagination.com> wrote: > It just occurred to me that a query cache issue could potentially > cause this... if it's caching it would most likely be a query.equals() > implementation incorrectly returning true. > Perhaps check the JaroWinkler.equals() first? > > Also, when one server starts to return bad results, have you tried > using explainOther=id:id_of_other_doc_that_should_score_higher? > > -Yonik > http://www.lucidimagination.com > > > On Tue, Apr 14, 2009 at 11:43 AM, Walter Underwood > <wunderw...@netflix.com> wrote: >> Dang, had another server do this. >> >> Syncing and committing a new index does not fix it. The two servers >> show the same bad results. >> >> wunder >> >> On 4/11/09 9:12 AM, "Walter Underwood" <wunderw...@netflix.com> wrote: >> >>> Restarting Solr fixes it. If I remember correctly, a sync and commit >>> does not fix it. I have disabled snappuller this time, so I can study >>> the broken instance. >>> >>> wunder
