[
https://issues.apache.org/jira/browse/SOLR-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093533#comment-14093533
]
Steve Davids commented on SOLR-6312:
------------------------------------
bq. So, if my understanding is correct, what you should be seeing is that
queries are randomly distributed to any 1 solr node, while updates are always
targeted at the correct leader.
[~hossman] You are correct, that is what I am seeing as well. Though I have a
re-indexing use-case where I would actually like to distribute update requests
to more than just the leader. I am currently performing XPath extraction logic
in the update chain before distributed the requests to replicas, the problem I
am running into is that the leader's CPU is completely pegged running the
XPaths while the replicas are almost idle (~20%). I looked to this feature to
allow more throughput by load balancing the extraction logic to the replicas
and just forwarding the complete/hydrated document to the leader. I know this
is a somewhat fringe case but still think it can be useful.
> CloudSolrServer doesn't honor updatesToLeaders constructor argument
> -------------------------------------------------------------------
>
> Key: SOLR-6312
> URL: https://issues.apache.org/jira/browse/SOLR-6312
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.9
> Reporter: Steve Davids
> Fix For: 4.10
>
>
> The CloudSolrServer doesn't use the updatesToLeaders property - all SolrJ
> requests are being sent to the shard leaders.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
