lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <>
Subject [jira] [Commented] (SOLR-3585) processing updates in multiple threads
Date Sun, 08 Jul 2012 19:37:35 GMT


David Smiley commented on SOLR-3585:

+1 (disclaimer: I haven't looked at the patch)

I've always thought Solr's indexing concurrency model to be strange. It doesn't have one,
except to say that each connection is on its own thread and thus happens concurrently with
any other connection(s).  Based on this model, SolrJ (and the DIH) has an unfair advantage
(compared to non-SolrJ) via StreamingUpdateSolrServer which can load Solr via multiple connections,
when this really should be a server-side setting since the ability of the server to handle
X number of loading threads is not something the client could/should know.  Solr should have
a configurable number of threads that pull Documents off of a common incoming queue.  This
patch is a step in that direction although it's not quite equivalent to my idealized vision.
> processing updates in multiple threads
> --------------------------------------
>                 Key: SOLR-3585
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: update
>    Affects Versions: 4.0
>            Reporter: Mikhail Khludnev
>            Priority: Minor
>         Attachments: 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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message