Re: NPE in QueryComponent.mergeIds when using timeAllowed and sorting SOLR 8.7

Patch looks good to me. Since it's a bugfix it can be committed to 8_8 branch and released on the next bugfix release, though I don't think it should trigger one. In the meantime, if you can patch your environment and confirm that it fixes your problem, that's a good comment to leave in SOLR-14758.

Re: NPE in QueryComponent.mergeIds when using timeAllowed and sorting SOLR 8.7

Anyone? > On Feb 24, 2021, at 7:47 AM, Phill Campbell > wrote: > > Last week I switched to Solr 8.7 from a “special” build of Solr 6.6 > > The system has a timeout set for querying. I am now seeing this bug. > > https://issues.apache.org/jira/browse/SOLR-14758 >

NPE in QueryComponent.mergeIds when using timeAllowed and sorting SOLR 8.7

Last week I switched to Solr 8.7 from a “special” build of Solr 6.6 The system has a timeout set for querying. I am now seeing this bug. https://issues.apache.org/jira/browse/SOLR-14758 Max Query Time goes from 1.6 seconds to 20 seconds and aff

NPE in QueryComponent.mergeIds when using timeAllowed and sorting SOLR 8.7

Last week I switched to Solr 8.7 from a “special” build of Solr 6.6 The system has a timeout set for querying. I am now seeing this bug. https://issues.apache.org/jira/browse/SOLR-14758 Max Query Time goes from 1.6 seconds to 20 seconds and aff

Re: "timeAllowed" param with "numFound" having a count value but doc list is empty

Hi, I am using timeAllowed and a collection with shards. Docs list contains results only if QTime(query time) < timeAllowed. In other cases (partialResults=true in responseHeader) docs are empty. /solr/collection_with_shards/select?etimeAllowed=1000&q=some_slow_query docs is empty If a

timeAllowed default value

Hi everyone, What is the default value for timeAllowed to make it behave as if it is not set? Is it "-1" or some other number? Rather than writing my code to include or not include timeAllowed in the query parameter, I rather have it be part of my query all the time and only change th

Re: TimeAllowed and Partial Results

TimeAllowed stops looking when the timer expires. If it hasn’t found any docs with a non-zero score by then, you’ll get zero hits. It has to be this way, because Solr doesn’t know whether a doc is a hit until Solr scores it. So this is normal behavior, assuming that some part of the processing

TimeAllowed and Partial Results

I have timeAllowed=2000 (2sec) and having mostly 0 hits coming out. Should I have more than 0 results? Jae

Re: "timeAllowed" param with "numFound" having a count value but doc list is empty

performance of your index, c) use timeAllowed and accept that queries > taking that long may fail or provide incomplete results, or d) a > combination of the above. > > If you use timeAllowed then you have to accept the possibility that a query > won't complete within the time a

Re: "timeAllowed" param with "numFound" having a count value but doc list is empty

Thanks much Bram! Best, Mark On Wed, Sep 16, 2020 at 3:59 AM Bram Van Dam wrote: > There are a couple of open issues related to the timeAllowed parameter. > For instance it currently doesn't work on conjunction with the > cursorMark parameter [1]. And on Solr 7 it doesn&#x

Re: "timeAllowed" param with "numFound" having a count value but doc list is empty

Hi Mark, If queries taking 10 (or however many) seconds isn't acceptable, then either you need to a) prevent or optimize those queries, b) improve the performance of your index, c) use timeAllowed and accept that queries taking that long may fail or provide incomplete results, or d) a combin

Re: "timeAllowed" param with "numFound" having a count value but doc list is empty

There are a couple of open issues related to the timeAllowed parameter. For instance it currently doesn't work on conjunction with the cursorMark parameter [1]. And on Solr 7 it doesn't work at all [2]. But other than that, when users have a lot of query flexibility, it's a pret

Re: "timeAllowed" param with "numFound" having a count value but doc list is empty

5:38 PM Dominique Bejean wrote: > Hi, > > 1. Yes, your analysis is correct > > 2. Yes, it can occurs too with very slow query. > > Regards > > Dominique > > Le mar. 15 sept. 2020 à 15:14, Mark Robinson a > écrit : > > > Hi, > > > > When

Re: "timeAllowed" param with "numFound" having a count value but doc list is empty

Hi, 1. Yes, your analysis is correct 2. Yes, it can occurs too with very slow query. Regards Dominique Le mar. 15 sept. 2020 à 15:14, Mark Robinson a écrit : > Hi, > > When in a sample query I used "timeAllowed" as low as 10mS, I got value for > > "numFound&

"timeAllowed" param with "numFound" having a count value but doc list is empty

Hi, When in a sample query I used "timeAllowed" as low as 10mS, I got value for "numFound" as say 2000, but no docs were returned. But when I increased the value for timeAllowed to be in seconds, never got this scenario. I have 2 qns:- 1. Why does numFound have a value like s

Re: About timeAllowed when using LTR

Hi, Dawn. It might make sense. Feel free to raise a jira, and "patches are welcome!". On Tue, Jun 30, 2020 at 10:33 AM Dawn wrote: > Hi: > > When using the LTR, open timeAllowed parameter, LTR feature of query may > call ExitableFilterAtomicReader. CheckAndThrow timeo

About timeAllowed when using LTR

Hi: When using the LTR, open timeAllowed parameter, LTR feature of query may call ExitableFilterAtomicReader. CheckAndThrow timeout detection. If a timeout occurs at this point, the exception ExitingReaderException is thrown, resulting in a no-result return. Is it possible to accommodate this

Re: Solr 8.5.1 query timeAllowed exceeded throws exception

ient.request(HttpSolrClient.java:265) > > at > org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:248) > > at > org.apache.solr.client.solrj.impl.LBSolrClient.doRequest(LBSolrClient.java:368) > > at > org.apache.solr.client.solrj.impl.LB

Re: Solr 8.5.1 query timeAllowed exceeded throws exception

t.request(HttpSolrClient.java:265) > > at > > org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:248) > > at > > org.apache.solr.client.solrj.impl.LBSolrClient.doRequest(LBSolrClient.java:368) > > at > > org.apache.solr.client.solrj.impl.LBSolrCli

Re: Solr 8.5.1 query timeAllowed exceeded throws exception

nt.java:248) > at > org.apache.solr.client.solrj.impl.LBSolrClient.doRequest(LBSolrClient.java:368) > at > org.apache.solr.client.solrj.impl.LBSolrClient.request(LBSolrClient.java:296) > > > The timeAllowed is set to 8 seconds. I am using a StopWatch to verify that > the round trip was greater than 8

Solr 8.5.1 query timeAllowed exceeded throws exception

org.apache.solr.client.solrj.impl.LBSolrClient.request(LBSolrClient.java:296) The timeAllowed is set to 8 seconds. I am using a StopWatch to verify that the round trip was greater than 8 seconds. Documentation states: timeAllowed Parameter This parameter specifies the amount of time, in milliseconds, allowed for a search to

Re: NPE on exceeding timeAllowed on SOLR-8.1.1

Hi, this is an issue (or a variation of it) that we encountered when using timeAllowed since we started using Solr (5 or 6). I see that there's a couple of JIRA issues that cover similar problems e.g. https://issues.apache.org/jira/browse/SOLR-9882 which is marked as resolved in 8.1. It'

NPE on exceeding timeAllowed on SOLR-8.1.1

(HttpSolrCall.java:542) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:397) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:343) *We are facing above error when we pass a complex query to SOLR with timeAllowed 30 seconds

Re: Understanding how timeAllowed works in a distributed cluster

Sorry I didn't understand your answer. Could you break that down a bit further. Thank you :) On Wed, Aug 22, 2018 at 11:53 PM Mikhail Khludnev wrote: > timeAllowed is not a realtime (as well as java per se). There is only a few > places which it can break. > > On Wed, Aug 22

Re: Understanding how timeAllowed works in a distributed cluster

timeAllowed is not a realtime (as well as java per se). There is only a few places which it can break. On Wed, Aug 22, 2018 at 4:09 PM Ash Ramesh wrote: > Hi again, > > Specs: 7.3.1 | 8 Shards | Solr Cloud > > I was wondering how the timeAllowed parameter works when you architect

Understanding how timeAllowed works in a distributed cluster

Hi again, Specs: 7.3.1 | 8 Shards | Solr Cloud I was wondering how the timeAllowed parameter works when you architect your cluster in a sharded and distributed manner. This is the curl command and the timing Query: http://localhost:9983/solr/media/select?fq=someField:someRedactedValue&q=*:

Re: Solr timeAllowed metric

facet.method=fc not facet.method=fsc are not, but facet.method=enum has a chance to be stopped when timeAllowed is exceeded. On Tue, Aug 7, 2018 at 9:40 AM Wei wrote: > Thanks Mikhail! Is traditional facet subject to timeAllowed? > > On Mon, Aug 6, 2018 at 3:46 AM, Mikhail Khludn

Re: Solr timeAllowed metric

Thanks Mikhail! Is traditional facet subject to timeAllowed? On Mon, Aug 6, 2018 at 3:46 AM, Mikhail Khludnev wrote: > One note: enum facets might be stopped by timeAllowed. > > On Mon, Aug 6, 2018 at 1:45 PM Mikhail Khludnev wrote: > > > Hello, Wei. > > > > "

Re: Solr timeAllowed metric

One note: enum facets might be stopped by timeAllowed. On Mon, Aug 6, 2018 at 1:45 PM Mikhail Khludnev wrote: > Hello, Wei. > > "Document collection" is done along side with "scoring process". So, Solr > will abort the request if > timeAllowed is exceeded

Re: Solr timeAllowed metric

Hello, Wei. "Document collection" is done along side with "scoring process". So, Solr will abort the request if timeAllowed is exceeded during the scoring process. Query, MLT, grouping are subject of timeAllowed constrains, but facet, json.facet https://issues.apache.org/ji

Solr timeAllowed metric

Hi, We tried to use solr's timeAllowed parameter to restrict the time spend on expensive queries. But as described at https://lucene.apache.org/solr/guide/6_6/common-query-parameters.html#CommonQueryParameters-ThetimeAllowedParameter " This value is only checked at the time of Query

Impact of timeAllowed parameter

Hi, Wondering how would be the calling application informed that the search request has been impacted due to time-out vs it has completed normally? Is there something that is sent to the client as part of the response that time-out has been invoked? Thanks

Using TimeAllowed parameter in SOLR-6.5.1

I started to use timeAllowed parameter in SOLR-6.5.1. And got too many (each second) exceptions null:java.lang.NullPointerException at org.apache.lucene.search.TimeLimitingCollector.needScores(TimeLimitingCollector.java:166) caused to perfomance problems. For reproducing exception need group

SOLR 6.5.1: timeAllowed parameter with grouping

A month ago we upgraded our SOLR from 4.10.1 to 6.5.1. Now we want to use timeAllowed parameter that was fixed in Solr 5. We check this parameter in test servers and we don't understand if it works with group=true or not. * If we set group=false and timeAllowed=1 and query with too

SOLR 6.5.1: timeAllowed parameter with grouping

A month ago we upgraded our SOLR from 4.10.1 to 6.5.1. Now we want to use timeAllowed parameter that was fixed in Solr 5. We check this parameter in test servers and we don't understand if it works with group=true or not. * If we set group=false and timeAllowed=1 and query with too

Re: NPE when using timeAllowed in the /export handler

I'd have to put some thought into this. The problem with timeAllowed is that it won't return all the results. So if you're using timeAllowed and performing a join or aggregation it will just give incorrect answers. I'm not we want to have that. Joel Bernstein http://joelsolr.b

Re: NPE when using timeAllowed in the /export handler

can you give some estimate on when they will be compatible . with out this, we cannot use timeAllowed with the map reduce mode of /sql handler right Thanks, Radhakrishnan D On Sat, Jan 21, 2017 at 6:03 PM, Joel Bernstein wrote: > I'm pretty sure that time allowed and the /export han

Re: NPE when using timeAllowed in the /export handler

I'm pretty sure that time allowed and the /export handler are not currently compatible. Joel Bernstein http://joelsolr.blogspot.com/ On Fri, Jan 20, 2017 at 8:57 PM, radha krishnan wrote: > Hi, > > am trying to query a core with 60 million docs by specifying timeAllowed as &g

NPE when using timeAllowed in the /export handler

Hi, am trying to query a core with 60 million docs by specifying timeAllowed as 100 ms just to test the timeAllowed feature. This is the query http://10.20.132.162:8983/solr/large_core/export?indent=on&q=*:*&distrib=false&fl=logtype&timeAllowed=100&sort=logtype+asc&wt=

Re: timeAllowed?

We use it on all requests. We are running 4.10.4 for most searches. We set a pretty high timeAllowed, either five or thirty seconds, depending on the service. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Nov 30, 2016, at 6:28 PM, William B

timeAllowed?

When should one use timeAllowed in Solr 5.5.3? How much overhead is involved in it? Does it create a thread and a timer event if you use it? Or is the timer event used even if you don't set it explicitly? We are thinking about using it for all requests. Just set it +10 milliseconds longer

Re: timeAllowed

ase-collection_2011", "hl.fl":"*", "wt":"json", "hl":"true", "rows":"10", "defType":"edismax", "expand.rows":"3", "hl.snippets":&q

Re: timeAllowed

artial results in the response. > Please let me know if you have any questions. > > Inline images 1 > > > Inline images 2 > > Regards, > Anil > > On 11 March 2016 at 19:13, Upayavira wrote: >> Show us the query URL. It would seem like your timeallowed >>

Re: timeAllowed

: > Show us the query URL. It would seem like your timeallowed isn't taking > effect. > > Upayavira > > On Fri, 11 Mar 2016, at 12:48 PM, Anil wrote: > > Thank you. > > > > in my test, i have timeallowed 10 ms. response has no partial results (no > > pa

Re: timeAllowed

Show us the query URL. It would seem like your timeallowed isn't taking effect. Upayavira On Fri, 11 Mar 2016, at 12:48 PM, Anil wrote: > Thank you. > > in my test, i have timeallowed 10 ms. response has no partial results (no > partial flag in the response header) and Qt

Re: timeAllowed

Thank you. in my test, i have timeallowed 10 ms. response has no partial results (no partial flag in the response header) and Qtime is 200 ms. so little confused. On 11 March 2016 at 18:07, Upayavira wrote: > > > On Fri, 11 Mar 2016, at 07:22 AM, Anil wrote: > > HI, > >

Re: timeAllowed

On Fri, 11 Mar 2016, at 07:22 AM, Anil wrote: > HI, > > is timeallowed is max threshold of Qtime ? or overall time ? Please > clarify. I do not understand the difference. Basically, when a query is happening, a collector gathers matching documents. The timeallowed parameter set

timeAllowed

HI, is timeallowed is max threshold of Qtime ? or overall time ? Please clarify. Thanks, Anil

timeAllowed behavior

Hey there, I'm a bit lots with timeAllowed lately. I'm not using solr cloud and have a monolitic index. I have the Solr version 4.5.1 in production. Now I'm testing Solr 5 and timeAllowed seems to behave different. In 4.5, when it was hit, it used to return the partial results i

Re: doubt about timeAllowed

Is there any way to tell timeAllow to just affect query component and not the others? -- View this message in context: http://lucene.472066.n3.nabble.com/doubt-about-timeAllowed-tp4257363p4257622.html Sent from the Solr - User mailing list archive at Nabble.com.

doubt about timeAllowed

the query taking too long (and timeAllowed working) but you would always get the highlighted part of the subset. With the latests versions, it can happen that due to the timeAllowed I get a subset of the results in the queryComponent but due to the timeAllowed too, I get no return on the

Re: How to check when a search exceeds the threshold of timeAllowed parameter

> > > > > > On 12/22/15, 5:43 PM, "Vincenzo D'Amore" wrote: > > >Well... I can write everything, but really all this just to understand > >when timeAllowed > >parameter trigger a partial answer? I mean, isn't there anything set in &

Re: How to check when a search exceeds the threshold of timeAllowed parameter

y all this just to understand >when timeAllowed >parameter trigger a partial answer? I mean, isn't there anything set in the >response when is partial? > >On Wed, Dec 23, 2015 at 2:38 AM, Walter Underwood >wrote: > >> We need to know a LOT more about your site. N

Re: How to check when a search exceeds the threshold of timeAllowed parameter

On 12/23/2015 01:42 AM, William Bell wrote: I agree that when using timeAllowed in the header info there should be an entry that indicates timeAllowed triggered. If I'm not mistaken, there is => partialResults:true "responseHeader":{ "partialResults":true } /

Re: How to check when a search exceeds the threshold of timeAllowed parameter

I agree that when using timeAllowed in the header info there should be an entry that indicates timeAllowed triggered. This is the only reason why we have not used timeAllowed. So this is a great suggestion. Something like: 1 ?? That would be great. 0 1 107 *:* 1000 On Tue, Dec 22, 2015 at

Re: How to check when a search exceeds the threshold of timeAllowed parameter

timeAllowed was designed to handle queries that by themselves consume lots of resources, not to try to handle situations with large numbers of requests that starve other requests from accessing CPU and I/O resources. The usual technique for handling large numbers of requests is replication

Re: How to check when a search exceeds the threshold of timeAllowed parameter

Well... I can write everything, but really all this just to understand when timeAllowed parameter trigger a partial answer? I mean, isn't there anything set in the response when is partial? On Wed, Dec 23, 2015 at 2:38 AM, Walter Underwood wrote: > We need to know a LOT more about y

Re: How to check when a search exceeds the threshold of timeAllowed parameter

when many > expensive searches clog the queue server becomes unresponsive. > > In order to quickly workaround this herd effect, I have added a > default timeAllowed to 15 seconds, and this seems help a lot. > > But during stress tests but I'm unable to understand when

How to check when a search exceeds the threshold of timeAllowed parameter

serve all these requests. As far as I know because some searches are very expensive, and when many expensive searches clog the queue server becomes unresponsive. In order to quickly workaround this herd effect, I have added a default timeAllowed to 15 seconds, and this seems help a lot. But during

Re: Query timeAllowed and its behavior.

12:29 PM, Erick Erickson > wrote: >> Hmmm, I took a whack at trying to create a unit test for this >> and I can't get it to fail. The test works like this >> >>> index 100 docs >>> send a query that exceeds timeAllowed >>> check that the stats on t

Re: Query timeAllowed and its behavior.

>> index 100 docs >> send a query that exceeds timeAllowed >> check that the stats on the queryResultCache show no inserts >> check that partial results are indicated >> check that the number of docs found < 100 >> re-send the same query with long timeAllowed &

Re: Query timeAllowed and its behavior.

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

Re: Query timeAllowed and its behavior.

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

Re: Query timeAllowed and its behavior.

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

Re: Query timeAllowed and its behavior.

, Modassar On Tue, Aug 25, 2015 at 4:46 PM, 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

Re:Query timeAllowed and its behavior.

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

Query timeAllowed and its behavior.

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

TimeAllowed bug

Weird fq caching bug when using timeAllowed Find a pwid (in this case YLGVQ) Run a query w/ a FQ on the pwid and timeAllowed=1. http://hgsolr2devsl.healthgrades.com:8983/solr/providersearch/select/?q=*:*&wt=json&fl=pwid&fq=pwid:YLGVQ&timeAllowed=1 Ensure #2 returns 0 results

Re: cursorMark and timeAllowed are mutually exclusive?

other options which prevent > getting a cursorMark? > > Yes, that was also my idea to set up a separate request handler > for harvesting without timeAllowed. > > As Shawn suggested, a short note about this should go into the documentation. > > Regards, > Bernd > >

Re: cursorMark and timeAllowed are mutually exclusive?

Thanks for your explanation. Right out of your head, are there any other options which prevent getting a cursorMark? Yes, that was also my idea to set up a separate request handler for harvesting without timeAllowed. As Shawn suggested, a short note about this should go into the documentation

Re: cursorMark and timeAllowed are mutually exclusive?

: > Have nothing found in the ref guides, docs, wiki, examples about this mutually : > exclusive parameters. : > : > Is this a bug or a feature and if it is a feature, where is the sense of this? The problem is that if a timeAllowed exceeded situation pops up, you won't get

Re: cursorMark and timeAllowed are mutually exclusive?

On 6/29/2015 9:12 AM, Bernd Fehling wrote: > while just trying cursorMark I got the following search response: > > "error": { > "msg": "Can not search using both cursorMark and timeAllowed", > "code": 400 > } > > > Yes, I&#

cursorMark and timeAllowed are mutually exclusive?

Hi list, while just trying cursorMark I got the following search response: "error": { "msg": "Can not search using both cursorMark and timeAllowed", "code": 400 } Yes, I'm using timeAllowed which is set in my requestHandler as invarian

Exception while using group with timeAllowed on SolrCloud

-timeAllowed-on-SolrCloud-tp4201570.html Sent from the Solr - User mailing list archive at Nabble.com.

Exception when using group.truncate with timeAllowed on SolrCloud

Hello, I am migrating from single node Solr to SolrCloud and have run into a problem. I have timeAllowed set to 5 minutes and am trying to facet on a string field. With grouping enabled and group.truncate set to true, I consistently get the following exception as soon as I fire the query. If I

Re: timeAllowed in not honoring

Apologies for late reply, Thanks Toke for a great explaination :) I am new in solr so i am unaware of DocValues, so please can you explain. With Regards Aman Tandon On Fri, May 2, 2014 at 1:52 PM, Toke Eskildsen wrote: > On Thu, 2014-05-01 at 23:03 +0200, Aman Tandon wrote: > > So can you expla

Re: timeAllowed in not honoring

On Thu, 2014-05-01 at 23:03 +0200, Aman Tandon wrote: > So can you explain how enum is faster than default. The fundamental difference is than enum iterates terms and counts how many of the documents associated to the terms are in the hits, while fc iterates all hits and updates a counter for the

Re: timeAllowed in not honoring

On Thu, 2014-05-01 at 23:38 +0200, Shawn Heisey wrote: > I was surprised to read that fc uses less memory. I think that is an error in the documentation. Except for special cases, such as asking for all facet values on a high cardinality field, I would estimate that enum uses less memory than fc.

Re: timeAllowed in not honoring

On 5/1/2014 3:03 PM, Aman Tandon wrote: > Please check that link > http://wiki.apache.org/solr/SimpleFacetParameters#facet.method there is > something mentioned in facet.method wiki > > *The default value is fc (except for BoolField which uses enum) since it > tends to use less memory and is faster

Re: timeAllowed in not honoring

Hi Shawn, Please check that link http://wiki.apache.org/solr/SimpleFacetParameters#facet.method there is something mentioned in facet.method wiki *The default value is fc (except for BoolField which uses enum) since it tends to use less memory and is faster then the enumeration method when a fiel

Re: timeAllowed in not honoring

On 4/30/2014 5:53 PM, Aman Tandon wrote: > Shawn -> Yes we have some plans to move to SolrCloud, Our total index size > is 40GB with 11M of Docs, Available RAM 32GB, Allowed heap space for solr > is 14GB, the GC tuning parameters using in our server > is -XX:+UseConcMarkSweepGC -XX:+PrintGCApplicat

Re: timeAllowed in not honoring

es wrote: > > It¹s not just FacetComponent, here¹s the original feature ticket for > timeAllowed: > https://issues.apache.org/jira/browse/SOLR-502 > > > As I read it, timeAllowed only limits the time spent actually getting > documents, not the time spent figuring out what data to

Re: timeAllowed in not honoring

It¹s not just FacetComponent, here¹s the original feature ticket for timeAllowed: https://issues.apache.org/jira/browse/SOLR-502 As I read it, timeAllowed only limits the time spent actually getting documents, not the time spent figuring out what data to get or how. I think that means the

Re: timeAllowed in not honoring

f time which is defined by this > timeAllowed parameter, but it doesn't seems to happen. Mikhail Khludnev has replied and explained why timeAllowed isn't stopping the query and returning partial results. A 14GB heap is quite large. If you aren't starting Solr with garbage collection

Re: timeAllowed in not honoring

On Wed, Apr 30, 2014 at 2:16 PM, Aman Tandon wrote: > name="time">3337.0 > 6739.0 > Most time is spent in facet counting. FacetComponent doesn't checks timeAllowed right now. You can try to experiment with facet.method=enum or even with htt

Re: timeAllowed in not honoring

0.0 0.0 0.00.0 0.0 10076.0 3337.0 6739.0 0.00.0 0.0 0.0 0.0 With Regards Aman Tandon On Wed, Apr 30, 2014 at

Re: timeAllowed in not honoring

I had this issue too. timeAllowed only works for a certain phase of the query. I think that's the 'process' part. However, if the query is taking time in 'prepare' phase (e.g. I think for wildcards to get all the possible combinations before running the query) it won'

Re: timeAllowed in not honoring

defined by this timeAllowed parameter, but it doesn't seems to happen. Here is the link : http://wiki.apache.org/solr/CommonQueryParameters#timeAllowed *The time allowed for a search to finish. This value only applies to the search and not to requests in general. Time is in milliseconds. Values

Re: timeAllowed in not honoring

On 4/29/2014 10:05 PM, Aman Tandon wrote: > I am using solr 4.2 with the index size of 40GB, while querying to my index > there are some queries which is taking the significant amount of time of > about 22 seconds *in the case of minmatch of 50%*. So i added a parameter > timeAllowed

timeAllowed in not honoring

Hi, I am using solr 4.2 with the index size of 40GB, while querying to my index there are some queries which is taking the significant amount of time of about 22 seconds *in the case of minmatch of 50%*. So i added a parameter timeAllowed = 2000 in my query but this doesn't seems to be

Re: timeAllowed query parameter not working?

n "XY" question. Perhaps a better thing to investigate is why this kind of query is considered useful and if there's any way to support that use case without trying this awful query :). Best, Erick On Thu, Mar 27, 2014 at 3:18 PM, Michael Ryan wrote: > Unfortunately the timeAllow

RE: timeAllowed query parameter not working?

Unfortunately the timeAllowed parameter doesn't apply to the part of the processing that makes wildcard queries so slow. It only applies to a later part of the processing when the matching documents are being collected. There's some discussion in the original ticket that implem

timeAllowed query parameter not working?

Hi Solr users, currently I have some really long running user entered pure wildcards queries (like *??) , these are hogging the CPU for several minutes. So what I tried is setting the "timeAllowed" query parameter via the search handler in solrconfig.xml. But without any luck, the

Re: Query time exceeds timeout specified by parameter timeAllowed

Hi Christof, In short: yes, known behaviour, you can't rely on timeAllowed as you'd think - it is limited to only a portion of total execution. See http://search-lucene.com/?q=timeallowed&sort=newestOnTop&fc_project=Solr for previous answers to this Q. Otis -- Solr &

Query time exceeds timeout specified by parameter timeAllowed

Hello, I just gave the parameter timeAllowed a try and noticed that in some cases the actual query time exceeds the timeout specified by the timeAllowed parameter, e.g., having set timeAllowed to 100 the actual query time is 300ms. Unfortunately, the documentation of the timeAllowed parameter is

Re: Solr 4.0 - timeAllowed in distributed search

Hi Michael, Thank you very much for your reply! Does it mean that when timeAllowed is used only search is interrupted and document retrieval is not? In order to check the total time of the query I run curl with linux time to measure the total time including retrieving of documents. If I

Re: Solr 4.0 - timeAllowed in distributed search

eval will almost always be the slowest > > part of the query. I'd suggest measuring how long it takes for the response > > to be returned, or use rows=0. > > > > The timeAllowed feature is very misleading. It only applies to a small > > portion of the query (whic

Re: Solr 4.0 - timeAllowed in distributed search

not include the time it > takes to retrieve these documents, but in a distributed search, it will. For > a *:* query, the document retrieval will almost always be the slowest part of > the query. I'd suggest measuring how long it takes for the response to be > returned, or use

RE: Solr 4.0 - timeAllowed in distributed search

. For a *:* query, the document retrieval will almost always be the slowest part of the query. I'd suggest measuring how long it takes for the response to be returned, or use rows=0. The timeAllowed feature is very misleading. It only applies to a small portion of the query (which

Re: timeAllowed flag in the response

Please file a JIRA. And a patch if you are so inclined. On Fri, Jun 8, 2012 at 4:55 AM, Michael Kuhlmann wrote: > Am 08.06.2012 11:55, schrieb Laurent Vaills: > >> Hi Michael, >> >> Thanks for the details that helped me to take a deeper look in the source >> code. I noticed that each time a TimeE

  1   2   >