Hello,
Sometimes we have "broken pipe" error when indexing 40 000 000 of documents
using ConcurrentUpdateSolrClient in java.
I have find on google that's probably is because à time out. But in
ConcurrentUpdateSolrClient we can't configure timeout.
For example the last
On 11/29/2016 4:47 AM, Srinivas Kashyap wrote:
> Can somebody guide me how to resolve this issue?
>
> Some of the parameters for Tomcat set are :
>
> maxWait="15000" maxActive="1000" maxIdle="50".
A broken pipe error usually means that the TCP connect
Hello,
After starting the solr application and running full imports, running into this
below error after a while:
null:org.apache.catalina.connector.ClientAbortException: java.io.IOException:
Broken pipe
at
org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:393
--
View this message in context:
http://lucene.472066.n3.nabble.com/Java-net-socketexception-broken-pipe-Solr-4-10-2-tp4199484p4200498.html
Sent from the Solr - User mailing list archive at Nabble.com.
on (netapp SAN with nfs exports on SAS
disk).
Broken pipe errors usually indicate that the client gave up waiting for
the server and disconnected the TCP connection before the server
completed processing and sent a response. This is frequently because of
configured timeouts on the client
-XX:NewRatio=3-XX:-UseSuperWord-Xmx5588m-Xms1596m
--
View this message in context:
http://lucene.472066.n3.nabble.com/Java-net-socketexception-broken-pipe-Solr-4-10-2-tp4199484p4199561.html
Sent from the Solr - User mailing list archive at Nabble.com.
-XX:TargetSurvivorRatio=90-XX:SurvivorRatio=4-XX:NewRatio=3-XX:-UseSuperWord-Xmx5588m-Xms1596m
--
View this message in context:
http://lucene.472066.n3.nabble.com/Java-net-socketexception-broken-pipe-Solr-4-10-2-tp4199484p4199561.html
Sent from the Solr - User mailing list archive
We upgraded recently to Solr 4.10.2 from 4.2.1 and have been seeing errors
regarding the dreaded broken pipe when doing our reindexing of all our
content.
Specifically:
ERROR - 2015-04-13 17:09:12.310;
org.apache.solr.update.StreamingSolrServers$1; error
java.net.SocketException: Broken pipe
).
--
View this message in context:
http://lucene.472066.n3.nabble.com/Java-net-socketexception-broken-pipe-Solr-4-10-2-tp4199484p4199485.html
Sent from the Solr - User mailing list archive at Nabble.com.
First ClientAbortException comes, which is expected as there is timeout on
client side with stack trace as follows
Jun 30, 2013 2:24:30 PM org.apache.solr.common.SolrException log
SEVERE: null:ClientAbortException: java.net.SocketException: Broken pipe
Any idea why I got a Broken pipe?
INFO - 2013-05-23 13:37:19.881; org.apache.solr.core.SolrCore;
[messages_shard3_replica1] webapp=/solr path=/select/
params={sort=score+descfl=id,smsc_module,smsc_modulekey,smsc_userid,smsc_ssid,smsc_description,smsc_description_ngram,smsc_content
Von: Arkadi Colson [ark...@smartbit.be]
Gesendet: Donnerstag, 23. Mai 2013 15:40
An: solr-user@lucene.apache.org
Betreff: Broken pipe
Any idea why I got a Broken pipe?
INFO - 2013-05-23 13:37:19.881; org.apache.solr.core.SolrCore;
[messages_shard3_replica1] webapp
@lucene.apache.org
Betreff: Broken pipe
Any idea why I got a Broken pipe?
INFO - 2013-05-23 13:37:19.881; org.apache.solr.core.SolrCore;
[messages_shard3_replica1] webapp=/solr path=/select/
params={sort=score+descfl=id,smsc_module,smsc_modulekey,smsc_userid,smsc_ssid,smsc_description
I had the same problem with jetty. It turned out that broken pipe happens when
application disconnects from jetty. In my case I was using php client and it
had 10 sec restriction in curl request. When solr takes more than 10 sec to
respond, curl automatically disconnected from jetty.
Hope
worried until I
realized the source of the problem.
Robi
-Original Message-
From: alx...@aim.com [mailto:alx...@aim.com]
Sent: Tuesday, July 03, 2012 10:38 AM
To: solr-user@lucene.apache.org
Subject: Re: Broken pipe error
I had the same problem with jetty. It turned out that broken pipe
Hi Guys,
We are experiencing SEVERE exceptions in SOLR (stacktrace below)
Please let me know if anyone has experienced this and have some insight /
pointers on to where and what should I look for to resolve this.
ERROR [solr.servlet.SolrDispatchFilter] - : java.io.IOException: XSLT
(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: javax.xml.transform.TransformerException: ClientAbortException:
java.net.SocketException: Broken pipe
at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:719
(OutputStreamWriter.java:229)
...
...
...
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
at java.net.SocketOutputStream.write(SocketOutputStream.java:153
)
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:140)
at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
...
...
...
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite
, broken pipe
It's not Jetty. It is broken TCP pipe due to client-side. It happens when
client
closes TCP connection.
And I even had this problem with recent Tomcat 6.
Problem disappeared after I explicitly tuned keep-alive at Tomcat, and started
using monitoring thread with HttpClient
20 matches
Mail list logo
