[
https://issues.apache.org/jira/browse/SOLR-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985866#comment-13985866
]
Joel Bernstein commented on SOLR-6035:
--------------------------------------
I should have some time in the next couple of days to test out the patch. One
of things we'll want to be sure of is that there aren't any issues caused by
going directly to coreUrl rather then through the collection Url. For exampe,
does replication within the shard still happen if you go 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: [email protected]
For additional commands, e-mail: [email protected]
