[
https://issues.apache.org/jira/browse/CONNECTORS-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557985#comment-13557985
]
Karl Wright commented on CONNECTORS-616:
----------------------------------------
I did a fair amount of research into this problem. It turns out that SolrJ is
working just fine. The problem seems to be on the Solr side - either Jetty or
Solr itself will occasionally drop connections if more than one of them come in
at the same time.
Since we don't have the luxury of waiting for the next Solr or Jetty release,
the fix I propose will instead simply work around the problem. ManifoldCF will
retry three times when a broken pipe is found, and give up on the document if
that isn't enough (because broken pipe can also mean that Solr crashed or
otherwise rejected the document for other reasons).
> 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
