[
https://issues.apache.org/jira/browse/SOLR-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038413#comment-14038413
]
David Smiley commented on SOLR-3585:
------------------------------------
[[email protected]] I'm thinking it would just be yet another URP that if
you want to use you have to add it; not by default -- let the masses try it
first. And you ask why not make StreamingSolrServer's use of CUSS
configurable? That's a good point. To me it's a matter of principle; let the
receiving end (the server) dictate the concurrency it can handle, not the
sender. And I like the idea of one peer-wise connection instead of 'N' as well.
> processing updates in multiple threads
> --------------------------------------
>
> Key: SOLR-3585
> URL: https://issues.apache.org/jira/browse/SOLR-3585
> Project: Solr
> Issue Type: Improvement
> Components: update
> Affects Versions: 4.0-ALPHA, 5.0
> Reporter: Mikhail Khludnev
> Attachments: SOLR-3585-oome-and-default-tests-chain.patch,
> SOLR-3585.patch, SOLR-3585.patch, SOLR-3585.patch, SOLR-3585.patch,
> SOLR-3585.patch, multithreadupd.patch, report.tar.gz
>
>
> Hello,
> I'd like to contribute update processor which forks many threads which
> concurrently process the stream of commands. It may be beneficial for users
> who streams many docs through single request.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
