[
https://issues.apache.org/jira/browse/SOLR-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667074#comment-13667074
]
Joel Bernstein edited comment on SOLR-4816 at 5/25/13 3:35 PM:
---------------------------------------------------------------
Requests are now threaded. Documents are batched up and routed to the correct
shard. Each routed request is sent in it's own thread so indexing on each Solr
server can be done in parallel.
With this scenario load throughput should increase almost linearly with cluster
size.
was (Author: joel.bernstein):
Request are now threaded. Documents are batched up and routed to the
correct shard. Each routed request is sent in it's own thread so indexing on
each Solr server can be done in parallel.
With this scenario load throughput should increase almost linearly with cluster
size.
> Add "directUpdate" capability to CloudSolrServer
> ------------------------------------------------
>
> Key: SOLR-4816
> URL: https://issues.apache.org/jira/browse/SOLR-4816
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.3
> Reporter: Joel Bernstein
> Priority: Minor
> Attachments: SOLR-4816.patch, SOLR-4816.patch, SOLR-4816.patch,
> SOLR-4816.patch, SOLR-4816.patch, SOLR-4816.patch, SOLR-4816.patch,
> SOLR-4816.patch, SOLR-4816.patch, SOLR-4816.patch, SOLR-4816.patch,
> SOLR-4816.patch, SOLR-4816.patch, SOLR-4816.patch, SOLR-4816.patch,
> SOLR-4816.patch, SOLR-4816-sriesenberg.patch
>
>
> This issue changes CloudSolrServer so it can optionally route update requests
> to the correct shard. This would be a nice feature to have to eliminate the
> document routing overhead on the Solr servers.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
