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 2014/05/01 17:05:21 UTC
[jira] [Commented] (SOLR-6035) CloudSolrServer directUpdate routing
should use getCoreUrl
[ https://issues.apache.org/jira/browse/SOLR-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986654#comment-13986654 ]
Joel Bernstein commented on SOLR-6035:
--------------------------------------
A review of the DistributedUpdateProcessor looks like it should handle going directly to the core.
The SolrDispatchFilter does attempt to pick out the leader core for a collection. If there are two leaders from the same collection in the same Solr instance then it could pick the wrong leader and this would cause the routing on the server side.
All tests are passing with patch. I'll do some manual testing, but so far so good.
Mark, let me know if you think I'm missing something.
> CloudSolrServer directUpdate routing should use getCoreUrl
> -----------------------------------------------------------
>
> Key: SOLR-6035
> URL: https://issues.apache.org/jira/browse/SOLR-6035
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Marvin Justice
> Assignee: Joel Bernstein
> Priority: Minor
> Labels: performance
> Attachments: SOLR-6035.patch, SOLR-6035.patch
>
>
> In a multisharded node environment we were seeing forward-to-leader hops when using CloudSolrServer directUpdate (with the hop being on the same node) . Consequently, there was no improvement in indexing performance over non-directUpdate.
> Changing buildUrlMap to use getCoreUrl eliminated the extra hop and now we see a dramatic improvement in performance.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org