You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by "Gesty, Jim" <jg...@cscinfo.com> on 2013/05/15 16:24:04 UTC
SEVERE:IOException occured when talking to server
We have a simple SolrCloud setup (4.1) running with a single shard and
multiple replicas across 3 servers, and it's working fine except once in a while,
the leader logs this error. We fine-tuned GC among other things and everything is lightning fast. However, we still receive this SEVERE error a few times a day.
15-May-2013 08:38:36.701 SEVERE [tomcat-http--6] org.apache.solr.common.SolrException.log shard update error StdNode: http://10.10.4.118:11280/solr/core1/:org.apache.solr.client.solrj.SolrServerException: IOException occured when talking to server at: http://10.10.4.118:11280/solr/core1
at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:416)
at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:181)
at org.apache.solr.update.SolrCmdDistributor$1.call(SolrCmdDistributor.java:332)
at org.apache.solr.update.SolrCmdDistributor$1.call(SolrCmdDistributor.java:306)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
Caused by: org.apache.http.NoHttpResponseException: The target server failed to respond
at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:101)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:282)
at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:216)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:647)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:732)
at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:353)
... 11 more
15-May-2013 08:38:36.706 INFO [tomcat-http--6] org.apache.solr.update.processor.DistributedUpdateProcessor.doFinish try and ask http://10.10.4.118:11280/solr to recover
15-May-2013 08:38:36.706 INFO [tomcat-http--6] org.apache.solr.client.solrj.impl.HttpClientUtil.createClient Creating new http client, config:maxConnections=128&maxConnectionsPerHost
Any ideas on what the root cause of this issue may be and how we can remediate it?
J
________________________________
NOTICE: This e-mail and any attachments is intended only for use by the addressee(s) named herein and may contain legally privileged, proprietary or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this email, and any attachments thereto, is strictly prohibited. If you receive this email in error please immediately notify me via reply email or at (800) 927-9800 and permanently delete the original copy and any copy of any e-mail, and any printout.
Re: SEVERE:IOException occured when talking to server
Posted by Mark Miller <ma...@gmail.com>.
I'd use Jetty for SolrCloud - much, much, much better tested.
Here is a note on something similar around tomcat: http://stackoverflow.com/questions/10570672/get-nohttpresponseexception-for-load-testing
Perhaps that helps, perhaps not.
The root cause is: org.apache.http.NoHttpResponseException: The target server failed to respond
- Mark
On May 15, 2013, at 10:24 AM, "Gesty, Jim" <jg...@cscinfo.com> wrote:
> We have a simple SolrCloud setup (4.1) running with a single shard and
> multiple replicas across 3 servers, and it's working fine except once in a while,
> the leader logs this error. We fine-tuned GC among other things and everything is lightning fast. However, we still receive this SEVERE error a few times a day.
>
>
> 15-May-2013 08:38:36.701 SEVERE [tomcat-http--6] org.apache.solr.common.SolrException.log shard update error StdNode: http://10.10.4.118:11280/solr/core1/:org.apache.solr.client.solrj.SolrServerException: IOException occured when talking to server at: http://10.10.4.118:11280/solr/core1
> at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:416)
> at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:181)
> at org.apache.solr.update.SolrCmdDistributor$1.call(SolrCmdDistributor.java:332)
> at org.apache.solr.update.SolrCmdDistributor$1.call(SolrCmdDistributor.java:306)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: org.apache.http.NoHttpResponseException: The target server failed to respond
> at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:101)
> at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
> at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:282)
> at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
> at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:216)
> at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
> at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
> at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:647)
> at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464)
> at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
> at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
> at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:732)
> at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:353)
> ... 11 more
>
> 15-May-2013 08:38:36.706 INFO [tomcat-http--6] org.apache.solr.update.processor.DistributedUpdateProcessor.doFinish try and ask http://10.10.4.118:11280/solr to recover
> 15-May-2013 08:38:36.706 INFO [tomcat-http--6] org.apache.solr.client.solrj.impl.HttpClientUtil.createClient Creating new http client, config:maxConnections=128&maxConnectionsPerHost
>
> Any ideas on what the root cause of this issue may be and how we can remediate it?
>
> J
>
> ________________________________
>
> NOTICE: This e-mail and any attachments is intended only for use by the addressee(s) named herein and may contain legally privileged, proprietary or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this email, and any attachments thereto, is strictly prohibited. If you receive this email in error please immediately notify me via reply email or at (800) 927-9800 and permanently delete the original copy and any copy of any e-mail, and any printout.