Can your provide some example expressions that are causing these exceptions?
Joel Bernstein http://joelsolr.blogspot.com/ On Wed, Jun 13, 2018 at 9:02 AM, Christian Spitzlay < christian.spitz...@biologis.com> wrote: > Hi, > > I am seeing a lot of (reproducible) exceptions in my solr log file > when I execute streaming expressions: > > o.a.s.s.HttpSolrCall Unable to write response, client closed connection > or we are shutting down > org.eclipse.jetty.io.EofException > at org.eclipse.jetty.io.ChannelEndPoint.flush( > ChannelEndPoint.java:292) > at org.eclipse.jetty.io.WriteFlusher.flush(WriteFlusher.java:429) > at org.eclipse.jetty.io.WriteFlusher.write(WriteFlusher.java:322) > at org.eclipse.jetty.io.AbstractEndPoint.write( > AbstractEndPoint.java:372) > at org.eclipse.jetty.server.HttpConnection$SendCallback. > process(HttpConnection.java:794) > […] > at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run( > EatWhatYouKill.java:131) > at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ > ReservedThread.run(ReservedThreadExecutor.java:382) > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob( > QueuedThreadPool.java:708) > at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run( > QueuedThreadPool.java:626) > at java.base/java.lang.Thread.run(Thread.java:844) > Caused by: java.io.IOException: Broken pipe > at java.base/sun.nio.ch.FileDispatcherImpl.writev0(Native Method) > at java.base/sun.nio.ch.SocketDispatcher.writev( > SocketDispatcher.java:51) > at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:148) > at java.base/sun.nio.ch.SocketChannelImpl.write( > SocketChannelImpl.java:506) > at org.eclipse.jetty.io.ChannelEndPoint.flush( > ChannelEndPoint.java:272) > ... 69 more > > > I have read up on the exception message and found > http://lucene.472066.n3.nabble.com/Unable-to-write-response-client-closed- > connection-or-we-are-shutting-down-tt4350349.html#a4350947 > but I don’t understand how an early client connect can cause what I am > seeing: > > What puzzles me is that the response has been delivered in full to the > client library, including the document with EOF. > > So Solr must have already processed the streaming expression and returned > the result. > It’s just that the log is filled with stacktraces of this exception that > suggests something went wrong. > I don’t understand why this happens when the query seems to have succeeded. > > > Best regards, > Christian > > >
