[
https://issues.apache.org/jira/browse/CONNECTORS-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560594#comment-13560594
]
Karl Wright commented on CONNECTORS-616:
----------------------------------------
Here's the scenario I think is happening. Remember that for each Solr
connection, we have a pool of httpclient connections on the client side, with
only 1 connection in it:
- The connection is opened to Solr
- The data is sent to Solr
- Solr sends the response back
- The connection is returned to the pool
- The existing connection is taken from the pool
- The client starts to send another file worth of data to Solr
- Solr does something crazy: it CLOSES the socket, for some reason, maybe as
part of finishing up the PREVIOUS transaction
- The client gets an IOException
If Solr is doing this it is wrong behavior anyhow, but one workaround is to
ALWAYS use a new connection. Unfortunately that has its costs - more setup
time, and more server-side handles are needed (we don't know how many more
exactly). So if IOExceptions happen all the time, it might be worth it, but if
IOExceptions are infrequent, then we are better with the current approach.
> Solr Connector gets broken pipe IOExceptions a lot
> --------------------------------------------------
>
> Key: CONNECTORS-616
> URL: https://issues.apache.org/jira/browse/CONNECTORS-616
> Project: ManifoldCF
> Issue Type: Bug
> Components: Lucene/SOLR connector
> Affects Versions: ManifoldCF 1.1
> Reporter: Karl Wright
> Assignee: Karl Wright
> Priority: Blocker
> Fix For: ManifoldCF 1.1
>
>
> Simple history is showing the following:
> {code}
> 01-18-2013 11:27:37.444 document ingest (1)
> file://///192.168.11.5/Sales/1-Quote/Quote-AAA.xls
> FAILED 16896 3 IOException occured when talking to server at:
> http://localhost:8983/solr: Broken pipe
> 01-18-2013 11:27:37.256 document ingest (1)
> file://///192.168.11.5/Sales/1-Quote/Quote-BBB.xls
> FAILED 16896 2 IOException occured when talking to server at:
> http://localhost:8983/solr: Broken pipe
> {code}
> Broken pipe exceptions should be being considered a Solr document rejection,
> akin to a 4xx error code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
