[
https://issues.apache.org/jira/browse/SOLR-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094170#comment-14094170
]
Erick Erickson commented on SOLR-6312:
--------------------------------------
Hmmm, interesting problem here. This is why, for scaling purposes, I vastly
prefer doing any such heavy lifting on the clients so I can scale up by racking
N clients together rather than have a Solr node be a bottleneck due to the
parsing. Is that a possibility?
So I suspect we can close this JIRA? You're correct that updatesToLeaders
is not respected, but it's also not going to be. Or perhaps change the title
to "depecrate CloudSolrServer updatesToLeaders constructor argument".
> 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]
