[
https://issues.apache.org/jira/browse/SOLR-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093503#comment-14093503
]
Steve Rowe commented on SOLR-6312:
----------------------------------
bq. I think the bug here is mark the updatesToLeaders option deprecated, and
remove it in trunk.
The updatesToLeader option has been disconnected from the way CloudSolrServer
operates for 11 months now, 5 feature releases ago - what's the point of
deprecating non-existent functionality?
(Jessica Cheng noted this problem a ways back [on
SOLR-4816|https://issues.apache.org/jira/browse/SOLR-4816?focusedCommentId=13792911&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13792911].)
I vote for outright removal - that should have happened when SOLR-4816 was
committed in [r1521713|http://svn.apache.org/r1521713].
> 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]
