[
https://issues.apache.org/jira/browse/CONNECTORS-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561371#comment-13561371
]
Karl Wright commented on CONNECTORS-616:
----------------------------------------
bq. FWIW I tried to use Solr 3.1 and SOLR REJECTs still be produced.
Then it is clear then that this problem has been in Solr for a long time, and
has been masked by the automatic retries the client has been doing. The
retries are visible now, and don't take place quite so quickly, is the only
difference.
I will take some time maybe this weekend to look through Solr servlet code to
find out where this happens and propose a patch.
> 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
