e of
>> the content and query-time deduplication, some queries could take hours
>> -that's 72 billion objects on a 2U box for you. Hope they've added better
>> index-time deduplication by now.
>> >
>> > Thanks,
>> >
>> > -dan
>> >
&
, some queries could take hours
> -that's 72 billion objects on a 2U box for you. Hope they've added better
> index-time deduplication by now.
> >
> > Thanks,
> >
> > -dan
> >
> > -----Original Message-
> > From: Mikhail Khludnev [mailt
ime deduplication by now.
>
> Thanks,
>
> -dan
>
> -Original Message-
> From: Mikhail Khludnev [mailto:m...@apache.org]
> Sent: Thursday, November 17, 2016 6:55 AM
> To: solr-user
> Subject: Re: How to stop long running/memory eating query
>
> There is a circ
org]
Sent: Thursday, November 17, 2016 6:55 AM
To: solr-user
Subject: Re: How to stop long running/memory eating query
There is a circuit breaker
https://cwiki.apache.org/confluence/display/solr/Common+Query+Parameters#CommonQueryParameters-ThetimeAllowedParameter
If I'm right, it does not interrup
There is a circuit breaker
https://cwiki.apache.org/confluence/display/solr/Common+Query+Parameters#CommonQueryParameters-ThetimeAllowedParameter
If I'm right, it does not interrupt faceting.
On Thu, Nov 17, 2016 at 2:07 PM, Susheel Kumar
wrote:
> Hello,
>
> We found a query which was running fo
Hello,
We found a query which was running forever and thus causing OOM (
q=+AND++AND+Tom+AND+Jerry...). Is there any way similar to SQL/No SQL
world where we can watch currently executed queries and able to kill them.
This can be desiring feature in these situations and avoid whole cluster
going
