You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Joel Bernstein (JIRA)" <ji...@apache.org> on 2013/05/29 04:18:20 UTC
[jira] [Comment Edited] (SOLR-4816) ConcurrentUpdateCloudSolrServer
[ https://issues.apache.org/jira/browse/SOLR-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13668927#comment-13668927 ]
Joel Bernstein edited comment on SOLR-4816 at 5/29/13 2:17 AM:
---------------------------------------------------------------
This implementation returns all the exceptions that occur as part of the response. You can see each exception and see which server it came from.
It also returns the routes that were used so you can see which docs were routed to which server. Very useful for testing.
was (Author: joel.bernstein):
This implementation returns all the exceptions that occur as part of the response. You can see each exception and see which server it came from.
It also returns the routes that were used so you can see which docs where routed to which server. Very useful for testing.
> ConcurrentUpdateCloudSolrServer
> -------------------------------
>
> 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.patch, SOLR-4816.patch, SOLR-4816.patch, SOLR-4816-sriesenberg.patch
>
>
> This issue adds a new Solr Cloud client called the ConcurrentUpdateCloudSolrServer. This Solr Cloud client implements document routing in the client so that document routing overhead is eliminated on the Solr servers. Documents are batched up for each shard and then each batch is sent in it's own thread.
> With this client, Solr Cloud indexing throughput should scale linearly with cluster size.
> This client also has robust failover built-in because the actual requests are made using the LBHttpSolrServer. The list of urls used for the request to each shard begins with the leader and is followed by that shard's replicas. So the leader will be tried first and if it fails it will try the replicas.
> Sample usage:
> ConcurrentUpdateCloudServer client = new ConcurrentUpdateCloudSolrServer(zkHostAddress);
> UpdateRequest request = new UpdateRequest();
> SolrInputDocument doc = new SolrInputDocument();
> doc.addField("id", 2);
> doc.addField("manu","BMW");
> request.add(doc);
> NamedList response = client.request(request);
> NamedList exceptions = response.get("exceptions"); // contains any exceptions from the shards
> NamedList responses = response.get("responses"); // contains the responses from shards without exception.
>
--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org