lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramkumar Aiyengar (JIRA)" <>
Subject [jira] [Commented] (SOLR-6035) CloudSolrServer directUpdate routing should use getCoreUrl
Date Wed, 30 Apr 2014 18:54:14 GMT


Ramkumar Aiyengar commented on SOLR-6035:

As far as I understand `DistributedUpdateProcessor`, indexing to the core itself would take
care of replication just fine. But of course, a test confirming this will be good..

> CloudSolrServer directUpdate routing should use getCoreUrl 
> -----------------------------------------------------------
>                 Key: SOLR-6035
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message