[
https://issues.apache.org/jira/browse/SOLR-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657115#action_12657115
]
Shalin Shekhar Mangar commented on SOLR-906:
--------------------------------------------
bq. why not? All the tests pass for me...
There are multiple places where SolrExampleTest calls commit without
waitSearcher=true and proceeds to query and assert on results. The failure
happens intermittently. Try varying the number of threads and you may be able
to reproduce the failure.
bq. The add calls do not come to the process method.
I meant the request method. Sorry about that. The SolrServer.add() calls the
request method but this implementation does not. If there are multiple threads
using this class, new documents may get added to the queue before we acquire
the lock inside blockUntilFinished due to the call to commit.
> Buffered / Streaming SolrServer implementaion
> ---------------------------------------------
>
> Key: SOLR-906
> URL: https://issues.apache.org/jira/browse/SOLR-906
> Project: Solr
> Issue Type: New Feature
> Components: clients - java
> Reporter: Ryan McKinley
> Assignee: Shalin Shekhar Mangar
> Fix For: 1.4
>
> Attachments: SOLR-906-StreamingHttpSolrServer.patch,
> SOLR-906-StreamingHttpSolrServer.patch, StreamingHttpSolrServer.java
>
>
> While indexing lots of documents, the CommonsHttpSolrServer add(
> SolrInputDocument ) is less then optimal. This makes a new request for each
> document.
> With a "StreamingHttpSolrServer", documents are buffered and then written to
> a single open Http connection.
> For related discussion see:
> http://www.nabble.com/solr-performance-tt9055437.html#a20833680
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
