You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2014/04/30 18:34:23 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=13985704#comment-13985704 ] 

Mark Miller commented on SOLR-6035:
-----------------------------------

Interesting - that may explain some earlier reports.

> 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
>            Priority: Minor
>              Labels: performance
>         Attachments: 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