Mikhail, If the query is not asynchronous, it would certainly be OK to stop the long-running query if the client socket is disconnected. I know that is a feature of the niche indexer used in the products of www.indexengines.com, because I wrote it. We did not have asynchronous queries, and because 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 -----Original Message----- From: Mikhail Khludnev [mailto:m...@apache.org] Sent: Thursday, November 17, 2016 6:55 AM To: solr-user <solr-user@lucene.apache.org> 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 interrupt faceting. On Thu, Nov 17, 2016 at 2:07 PM, Susheel Kumar <susheel2...@gmail.com> wrote: > 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 down. Is there any existing JIRA/can create one. > > Also what would be the different ways we can examine and stop such > queries to execute. > > Thanks, > Susheel > -- Sincerely yours Mikhail Khludnev
