Solr connection timeout while indexing?

I have a solrj client with infinite timeout (Solr4)

server.server.setSoTimeout(0)
server.server.setConnectionTimeout(0)

      

When I index my data I have a lot of server side timeouts. Where can I update the server side timeouts in the solrconfig.xml file or in a possible tomcat config?

Client side exclusion:

Caused by: java.net.SocketException: Broken pipe
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
    at java.net.SocketOutputStream.write(SocketOutputStream.java:136)

      

Server side exception:

 Jan 31, 2013 8:55:54 PM org.apache.solr.common.SolrException log
    SEVERE: org.apache.solr.common.SolrException: Read timed out
        at org.apache.solr.handler.loader.XMLLoader.load(XMLLoader.java:159)
        at org.apache.solr.handler.UpdateRequestHandler$1.load(UpdateRequestHandler.java:92)
        at org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:74)
        at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:129)
        at org.apache.solr.core.SolrCore.execute(SolrCore.java:1699)
Caused by: java.net.SocketTimeoutException: Read timed out
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:129)
    at org.apache.coyote.http11.InternalInputBuffer.fill(InternalInputBuffer.java:751)

      

+3


source to share


2 answers


information for tomcat server.xml config will solve this. we got the same stack trace and below it resolved it for us: http://forums.alfresco.com/ja/node/8458



0


source


We had the same problem with Solr 4. We solved it after reading the blog post by Uwe Schindler (Solr committer).



With Solr 4 and several versions of Solr 3, you must free up an important chunk of your RAM so the system can use the mmap system call correctly . This can be subtle depending on your system configuration (the blog post gives a lot of information on this). In our case, this solved the problem: we could finally index without any timeout issues.

0


source







All Articles