Large number of range facets causes server to lock up
-----------------------------------------------------
Key: SOLR-2855
URL: https://issues.apache.org/jira/browse/SOLR-2855
Project: Solr
Issue Type: Bug
Components: SearchComponents - other
Affects Versions: 3.4
Reporter: Bernhard Frauendienst
(NOTE: I'm aware that this is not exactly a BUG in the sense that something is
not working correctly, but it is still something that might be considered to be
changed.)
A bug in our code triggered an integer overflow which caused very large range
facets to be requested on a TrieIntField
(e.g.
{{facet.range.start=*-2147483648*&facet.range.end=1000&facet.range.gap=1}})
This caused the Solr server to allocate huge amounts of memory so that it soon
had filled up the whole 18 GB the JVM had available, and the Garbage Collector
wasn't able to free it (fast enough?) and was thus taking up nearly all of the
CPU, which finally led to a complete Denial of Service.
While the cause for this behavior obviously lies within the buggy code, it
might still be desirable for Solr not to lock up for "wrong" parameters but
throw an error instead.
Throwing an exception if more ranges than the {{facet.limit}} value (or a
similar, new parameter) for this field would be generated might be a good
solution.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
