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=30000 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 - when they are truncated. SEEMS LIKE A BUG TO ME. On Tue, Aug 25, 2015 at 5:16 AM, Jonathon Marks (BLOOMBERG/ LONDON) < jmark...@bloomberg.net> wrote: > timeAllowed applies to the time taken by the collector in each shard > (TimeLimitingCollector). Once timeAllowed is exceeded the collector > terminates early, returning any partial results it has and freeing the > resources it was using. > From Solr 5.0 timeAllowed also applies to the query expansion phase and > SolrClient request retry. > > From: solr-user@lucene.apache.org At: Aug 25 2015 10:18:07 > Subject: Re:Query timeAllowed and its behavior. > > Hi, > > Kindly help me understand the query time allowed attribute. The following > is set in solrconfig.xml. > <int name="timeAllowed">300000</int> > > 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, > Modassar > > > -- Bill Bell billnb...@gmail.com cell 720-256-8076
