Re: “ClientAbortException: java.io.IOException” in solr query

[Shawn Heisey <so...@elyograg.org>]

On 8/3/2013 7:18 AM, Alexandre Rafalovitch wrote:
> The client closed the web-browser page or stopped loading or some other
> timeout/connection close. Then, the server tries to write to no-longer
> existing connection and fails.
> 
> If you control the client, then you might have some sort of timeout value,
> which kills connections after very long queries.
> 
> Regards,
>    Alex.
> 
> Personal website: http://www.outerthoughts.com/
> LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch
> - Time is the quality of nature that keeps events from happening all at
> once. Lately, it doesn't seem to be working.  (Anonymous  - via GTD book)
> 
> 
> On Fri, Aug 2, 2013 at 11:46 PM, aniljayanti <an...@yahoo.co.in>wrote:
> 
>> Hi,
>>
>> I am generating solr indexing using apache-tomcat-7.0.19 and solr 3.3.
>> Indexing generated successfully with count of "3350128" records. Now i am
>> testing my solr index search performance continuously by hitting with
>> different search queries.
>>
>> while testing some search queries are getting failed, and getting below
>> error in tomcat error logs.
>>
>> org.apache.solr.common.SolrException log
>> SEVERE: ClientAbortException:  java.io.IOException

I second what Alexandre said.  Here's Tomcat's own javadoc saying the
same thing:

https://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/catalina/connector/ClientAbortException.html

The specific part of this javadoc that is relevant here: "Wrap an
IOException identifying it as being caused by an abort of a request by a
remote client."

The client making the query chose to disconnect before Solr had
responded.  You may need to increase the timeout on the client.  The
only thing you can do on the Solr end is make the query respond faster,
which is a performance issue.  Usually (but not always), performance
issues are caused by some variation of "not enough memory."

http://wiki.apache.org/solr/SolrPerformanceProblems

Thanks,
Shawn