lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marvin Justice (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-6035) CloudSolrServer directUpdate routing should use getCoreUrl
Date Wed, 30 Apr 2014 20:37:28 GMT

    [ https://issues.apache.org/jira/browse/SOLR-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986042#comment-13986042
] 

Marvin Justice commented on SOLR-6035:
--------------------------------------

Just spun up a 4 shard x 2 replica test collection. Replication seems to be working just fine
for me when going directly to the coreUrl. 

> 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
>
>
> 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


Mime
View raw message