See: https://issues.apache.org/jira/browse/SOLR-7990
On Sat, Aug 29, 2015 at 1:04 PM, Erick Erickson wrote:
> OK, belay that. On a whim I decided to look at what happens if
> I changed things around to use an fq clause. It's apparently
> not the queryResultCache that's the problem, it's the filt
OK, belay that. On a whim I decided to look at what happens if
I changed things around to use an fq clause. It's apparently
not the queryResultCache that's the problem, it's the filterCache.
Raising a JIRA soon. But I'm not sure where things are going
wrong, the filterCache stats aren't indicating
On 8/28/2015 10:47 PM, William Bell wrote:
> As we reported, we are having issues with timeAllowed on 5.2.1. If we set a
> timeAllowed=1 and then run the same query with timeAllowed=3 we get the
> # of rows that was returned on the first query.
>
> It appears the results are cached when exceed
As we reported, we are having issues with timeAllowed on 5.2.1. If we set a
timeAllowed=1 and then run the same query with timeAllowed=3 we get the
# of rows that was returned on the first query.
It appears the results are cached when exceeding the timeAllowed, like the
results are correct - w
On 8/25/2015 3:18 AM, Modassar Ather wrote:
> Kindly help me understand the query time allowed attribute. The following
> is set in solrconfig.xml.
> 30
>
> Does this setting stop the query from running after the timeAllowed is
> reached? If not is there a way to stop it as it will occupy resou
Thanks for your response Jonathon.
Please correct me if I am wrong in following points.
-query actually ceases to run once time allowed is reached and releases
all the resources.
-query expansion is stopped and the query is terminated from execution
releasing all the resources.
Thanks,
Moda
Hi,
Kindly help me understand the query time allowed attribute. The following
is set in solrconfig.xml.
30
Does this setting stop the query from running after the timeAllowed is
reached? If not is there a way to stop it as it will occupy resources in
background for no benefit.
Thanks,
Modass
