On 7/2/2021 5:14 AM, Ma, Samuel wrote:
Hi, Solr users I have a oom issue in SolrIndexSearcher.buildTopDocsCollector in Solr7.7.2, I can see the stack is from below:
If you're experiencing OutOfMemoryError, it is extremely unlikely that investigating the stacktrace where it happened will tell you what caused the exception. Do you have the full text of the exception? The first part of it is missing in what you pasted. That part will tell you what resource was exhausted, which will tell you what resource you need to increase.
The reason that the stacktrace in the exception is usually not helpful is that the place where the exception is thrown is merely the final straw -- where the program execution was at the precise moment the resource was depleted. Chances are that it was a different place in the program where the major resource allocations occurred.
Here I just do not understand why the len in QueryCommand (The second parameter for SolrIndexSearcher.buildTopDocsCollector) is MAX integer 2147483647. Can you help me? Thank you!
The javadoc description of that parameter is "maximum number of documents to return" ... whatever called it doesn't want to limit the number of results, so it's asking for the maximum number that it can. This does not look to me like a problem.
Thanks, Shawn
