You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2013/08/01 14:05:48 UTC
[jira] [Resolved] (SOLR-5100) java.lang.OutOfMemoryError: Requested
array size exceeds VM limit
[ https://issues.apache.org/jira/browse/SOLR-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erick Erickson resolved SOLR-5100.
----------------------------------
Resolution: Invalid
Please raise this on the user's list. OOM errors are common when one has not allocated enough heap to the JVM or otherwise tries to do too much with too few resources. The user's list will offer lots of help to change your setup to no longer OOM.
> java.lang.OutOfMemoryError: Requested array size exceeds VM limit
> -----------------------------------------------------------------
>
> Key: SOLR-5100
> URL: https://issues.apache.org/jira/browse/SOLR-5100
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.2.1
> Environment: Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 GNU/Linux
> Java 7, Tomcat, ZK standalone
> Reporter: Grzegorz Sobczyk
>
> Today I found exception in log (lmsiprse01):
> {code}
> sie 01, 2013 5:27:26 AM org.apache.solr.core.SolrCore execute
> INFO: [products] webapp=/solr path=/select params={facet=true&start=0&q=&facet.limit=-1&facet.field=attribute_u-typ&facet.field=attribute_u-gama-kolorystyczna&facet.field=brand_name&wt=javabin&fq=node_id:1056&version=2&rows=0} hits=1241 status=0 QTime=33
> sie 01, 2013 5:27:26 AM org.apache.solr.common.SolrException log
> SEVERE: null:java.lang.RuntimeException: java.lang.OutOfMemoryError: Requested array size exceeds VM limit
> at org.apache.solr.servlet.SolrDispatchFilter.sendError(SolrDispatchFilter.java:653)
> at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:366)
> at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:141)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> at java.lang.Thread.run(Thread.java:724)
> Caused by: java.lang.OutOfMemoryError: Requested array size exceeds VM limit
> at org.apache.lucene.util.PriorityQueue.<init>(PriorityQueue.java:64)
> at org.apache.lucene.util.PriorityQueue.<init>(PriorityQueue.java:37)
> at org.apache.solr.handler.component.ShardFieldSortedHitQueue.<init>(ShardDoc.java:113)
> at org.apache.solr.handler.component.QueryComponent.mergeIds(QueryComponent.java:766)
> at org.apache.solr.handler.component.QueryComponent.handleRegularResponses(QueryComponent.java:625)
> at org.apache.solr.handler.component.QueryComponent.handleResponses(QueryComponent.java:604)
> at org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:311)
> at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
> at org.apache.solr.core.SolrCore.execute(SolrCore.java:1817)
> at org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:639)
> at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:345)
> ... 13 more
> {code}
> We have:
> * 3x standalone zK
> * 3x Solr 4.2.1 on Tomcat
> Exception shows up after leader was stopped:
> * lmsiprse01:
> [2013-08-01 05:23:43]: /etc/init.d/tomcat6-1 stop
> [2013-08-01 05:25:09]: /etc/init.d/tomcat6-1 start
> * lmsiprse02 (leader):
> 2013-08-01 05:27:21]: /etc/init.d/tomcat6-1 stop
> 2013-08-01 05:29:31]: /etc/init.d/tomcat6-1 start
> * lmsiprse03:
> [2013-08-01 05:25:48]: /etc/init.d/tomcat6-1 stop
> [2013-08-01 05:26:42]: /etc/init.d/tomcat6-1 start
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org