Just opened the very core in a "normal" Solr server instance. Same delay till it's usable. I.e. nothing to do with embedded-mode or any other thread slowing down things
-----Ursprüngliche Nachricht----- Von: Clemens Wyss DEV [mailto:clemens...@mysign.ch] Gesendet: Sonntag, 3. Mai 2015 18:30 An: solr-user@lucene.apache.org Betreff: AW: "blocked" in org.apache.solr.core.SolrCore.getSearcher(...) ? No load by/on any other thread. In fact I have 4 cores in my (embedded) Solr. The other three, which contain "less" and "other" data, are up and running in "no time" (<1s) Sidenote: The "slow core" is being filled by 7500 pdfs (overall 24G) extracted with Tika. -----Ursprüngliche Nachricht----- Von: Yonik Seeley [mailto:ysee...@gmail.com] Gesendet: Sonntag, 3. Mai 2015 17:53 An: solr-user@lucene.apache.org Betreff: Re: "blocked" in org.apache.solr.core.SolrCore.getSearcher(...) ? What are the other threads doing during this time? -Yonik On Sun, May 3, 2015 at 4:00 AM, Clemens Wyss DEV <clemens...@mysign.ch> wrote: > Context: Solr 5.1, EmbeddedSolrServer(-mode) > > I have a rather big index/core (>1G). I was able to initially index this core > and could then search within it. Now when I restart my app I am no more able > to search. > getSearcher seems to "hang"... : > > java.lang.Object.wait(long) line: not available [native method] > java.lang.Object.wait() line: 502 > org.apache.solr.core.SolrCore.getSearcher(boolean, boolean, > java.util.concurrent.Future[], boolean) line: 1646 > org.apache.solr.core.SolrCore.getSearcher(boolean, boolean, > java.util.concurrent.Future[]) line: 1442 > org.apache.solr.core.SolrCore.getSearcher() line: 1377 > org.apache.solr.servlet.SolrRequestParsers$1(org.apache.solr.request.S > olrQueryRequestBase).getSearcher() line: 111 > org.apache.solr.handler.component.QueryComponent.process(org.apache.so > lr.handler.component.ResponseBuilder) line: 304 > org.apache.solr.handler.component.SearchHandler.handleRequestBody(org. > apache.solr.request.SolrQueryRequest, > org.apache.solr.response.SolrQueryResponse) line: 222 > org.apache.solr.handler.component.SearchHandler(org.apache.solr.handle > r.RequestHandlerBase).handleRequest(org.apache.solr.request.SolrQueryR > equest, org.apache.solr.response.SolrQueryResponse) line: 143 > org.apache.solr.core.SolrCore.execute(org.apache.solr.request.SolrRequ > estHandler, org.apache.solr.request.SolrQueryRequest, > org.apache.solr.response.SolrQueryResponse) line: 1984 > org.apache.solr.client.solrj.embedded.EmbeddedSolrServer.request(org.a > pache.solr.client.solrj.SolrRequest, java.lang.String) line: 177 > org.apache.solr.client.solrj.request.QueryRequest(org.apache.solr.clie > nt.solrj.SolrRequest).process(org.apache.solr.client.solrj.SolrClient, > java.lang.String) line: 135 > org.apache.solr.client.solrj.embedded.EmbeddedSolrServer(org.apache.so > lr.client.solrj.SolrClient).query(java.lang.String, > org.apache.solr.common.params.SolrParams) line: 943 > org.apache.solr.client.solrj.embedded.EmbeddedSolrServer(org.apache.so > lr.client.solrj.SolrClient).query(org.apache.solr.common.params.SolrParams) > line: 958 ... > > I am not seeing any "interesting" solr/lucene-log messages. > > What's possibly going wrong? Memory? Or does warming/starting up a searcher > take that long ... more than 15 minutes? > > Thx > Clemens
