[
https://issues.apache.org/jira/browse/SOLR-16216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542808#comment-17542808
]
Atri Sharma commented on SOLR-16216:
------------------------------------
This is actually a good idea.
Here are my thoughts on the same:
# It is very hard to track the memory usage of a single query (unless you do
something like the custom allocator that ElasticSearch does, which is a huge
change and can introduce overheads).
# An alternate way is to track the runtime of on going queries and in case of
a JVM threshold breach, kill the longest running ones. This is doable if we tie
in the circuit breaker mechanism to the query/task management mechanism, which
will allow tracking and killing queries.
> Circuit Breaker - Kill only the particular search requests crossing the
> circuit breaker threshold
> -------------------------------------------------------------------------------------------------
>
> Key: SOLR-16216
> URL: https://issues.apache.org/jira/browse/SOLR-16216
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Parag Ninawe
> Priority: Major
>
> This ticket is for feature improvement and help needed to handle the
> following condition
> Have an optional feature where in there is a provision to track the usage of
> the Solr Search request and kill the particular request if it crosses the
> threshold of resource usage.
> Also, Is there any other way we can handle the scenario where we reject only
> the query which crosses the JVM heap threshold which will eventually end up
> causing OOM issues.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
