[
https://issues.apache.org/jira/browse/CONNECTORS-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559615#comment-13559615
]
Karl Wright commented on CONNECTORS-616:
----------------------------------------
It is expected that, because of the Solr bugs, it will show SOLR REJECT on some
documents but will retry up to 3 times. This is the workaround I proposed. Do
you see any cases where a failed document did not actually get retried and
indexed?
Remember that there is no fix for this problem except for a new Lucene/Solr
release which addresses the issue. And nobody has yet even commented on the
tickets I have created for this problem in the SOLR queue.
I don't think we are using SolrJ incorrectly, and like I said I have
extensively reviewed the SolrJ code and found no problem with it that can
account for the behavior. There is no cross-thread activity. If you see the
same thing with Tomcat that means the bug is likely in Solr itself. I will
note that in the Solr ticket.
> 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
