lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christine Poerschke (JIRA)" <>
Subject [jira] [Commented] (SOLR-9770) Solr should not cache queries that fail
Date Tue, 15 Aug 2017 17:14:01 GMT


Christine Poerschke commented on SOLR-9770:

* appears to be the user list thread mentioned
in the description.
* In SOLR-11240 [~toke] outlines how the "Too many values for UnInvertedField" exception can
be triggered i.e. that could perhaps be used as a starting point for reproducing the autowarming
errors here e.g. in a test case perhaps.

> Solr should not cache queries that fail
> ---------------------------------------
>                 Key: SOLR-9770
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 6.4
>            Reporter: Erick Erickson
>            Priority: Minor
> Bram Van Dam on the user's list had a problem with a bad query causing an exception:
> java.lang.IllegalStateException: Too many values for UnInvertedField
> faceting on field text. 
> Then the query apparently got into one of the caches and was then autowarmed leading
to the error every time a new searcher was opened.
> This does _not_ happen with, say, a query that references an undefined field. Such a
query doesn't get into the cache in the first place.
> I have not been able to verified this but it seems worth a JIRA to investigate at least,
no query that throws an exception should get into the caches. You can imagine a situation
where this leads to OOM errors and Solr needing to be restarted to get past it.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message