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 > > On 4/11/09 5:03 AM, "Grant Ingersoll" <gsing...@apache.org> wrote: > >> >> On Apr 10, 2009, at 5:50 PM, Walter Underwood wrote: >> >>> Normally, both "changeling" and "the changeling" work fine. This one >>> server is misbehaving like this for all multi-term queries. >>> >>> Yes, it is VERY weird that the term "changeling" does not show up in >>> the explain. >>> >>> A server will occasionally "go bad" and stay in that state. In one >>> case, >>> two servers went bad and both gave the same wrong results. >>> >> >> What's the solution for when they go bad? Do you have to restart Solr >> or reboot or what? >> >> >>> Here is the dismax config. "groups" means "movies". The title* fields >>> are stemmed and stopped, the "exact*" fields are not. >>> >>> <!-- groups and people --> >>> >>> <requestHandler name="groups_people" class="solr.SearchHandler"> >>> <lst name="defaults"> >>> <str name="defType">dismax</str> >>> <str name="echoParams">none</str> >>> <float name="tie">0.01</float> >>> <str name="qf"> >>> exact^6.0 exact_alt^6.0 exact_base~jw_0.7_1^8.0 exact_alias^8.0 >>> title^3.0 title_alt^3.0 title_base^4.0 >>> </str> >>> >>> <str name="pf"> >>> exact^9.0 exact_alt^9.0 exact_base^12.0 exact_alias^12.0 >>> title^3.0 >>> title_alt^4.0 title_base^6.0 >>> </str> >>> <str name="bf"> >>> search_popularity^100.0 >>> </str> >>> <str name="mm">1</str> >>> <int name="ps">100</int> >>> <str name="fl">id,type,movieid,personid,genreid</str> >>> >>> </lst> >>> <lst name="appends"> >>> <str name="fq">type:group OR type:person</str> >>> </lst> >>> </requestHandler> >>> >>> >>> wunder >>> >>> On 4/10/09 12:51 PM, "Grant Ingersoll" <gsing...@apache.org> wrote: >>> >>>> >>>> On Apr 10, 2009, at 1:56 PM, Walter Underwood wrote: >>>> >>>>> We have a rare, hard-to-reproduce problem with our Solr 1.3 servers, >>>>> and >>>>> I would appreciate any ideas. >>>>> >>>>> Ocassionally, a server will start returning results with really poor >>>>> relevance. Single term queries work fine, but multi-term queries are >>>>> scored based on the most common term (lowest IDF). >>>>> >>>>> I don't see anything in the logs when this happens. We have a >>>>> monitor >>>>> doing a search for the 100 most popular movies once per minute to >>>>> catch this, so we know when it was first detected. >>>>> >>>>> I'm attaching two explain outputs, one for the query "changeling" >>>>> and >>>>> one for "the changeling". >>>> >>>> >>>> I'm not sure what exactly you are asking, so bear with me... >>>> >>>> Are you saying that "the changeling" normally returns results just >>>> fine and then periodically it will "go bad" or are you saying you >>>> don't understand why "the changeling" scores differently from >>>> "changeling"? In looking at the explains, it is weird that in the >>>> "the changeling" case, the term changeling doesn't even show up as a >>>> term. >>>> >>>> Can you share your dismax configuration? That will be easier to >>>> parse >>>> than trying to make sense of the debug query parsing. >>>> >>>> -Grant >>> >> >> -------------------------- >> Grant Ingersoll >> http://www.lucidimagination.com/ >> >> Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids) >> using Solr/Lucene: >> http://www.lucidimagination.com/search >> >
