[
https://issues.apache.org/jira/browse/SOLR-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13668747#comment-13668747
]
Mark Miller commented on SOLR-4816:
-----------------------------------
bq. The way Exceptions are handled in this patch is that each thread
With a new impl, we should consider how we want to do this carefully.
If we just go this route, it's really not much better the state the concurrent
solrserver is in. This could be a good time to introduce better handling for
concurrent solrservers - error detectiong and responses - you really still want
to know exactly what happened with your updates, and it's currently very
difficult to determine that. It's an improvement we have to get to, and it's
probably going to be a back compat headache - perhaps we start by introducing
something here and eventually this would become the standard client you want to
use.
> 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: [email protected]
For additional commands, e-mail: [email protected]
