[
https://issues.apache.org/jira/browse/SOLR-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094182#comment-14094182
]
Hoss Man commented on SOLR-6312:
--------------------------------
bq. So I suspect we can close this JIRA? You're correct that updatesToLeaders
is not respected, but it's also not going to be.
Steve's use case (and similar usecases like it, ie: using the
ExtractingRequestHandler on large binary data files) actually strikes me as a
really good reason to make upatesToLeaders==false meaningful again: randomize
updates to all "up" replicas in the collection regardless of leader status.
(the default is
upatesToLeaders=true, no reason that would change, no reason it would impact
anyone except people like steve trying to distribute the load of early logic to
non-leaders)
> 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]
