You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@solr.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2024/05/13 22:31:00 UTC

[jira] [Resolved] (SOLR-11999) RebalanceLeaders API should not require a preferredLeader property

     [ https://issues.apache.org/jira/browse/SOLR-11999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Smiley resolved SOLR-11999.
---------------------------------
    Resolution: Won't Fix

This doesn't seem useful.  Without preferredLeader, leadership assignment is very arbitrary and unstable.  So why not use preferredLeader?  If it's because it wasn't assigned in the first place, well yeah, you should do that then!  Let's make it easier to assign a preferred leader. 

Marking as won't-fix; feel free to re-open.


> RebalanceLeaders API should not require a preferredLeader property
> ------------------------------------------------------------------
>
>                 Key: SOLR-11999
>                 URL: https://issues.apache.org/jira/browse/SOLR-11999
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>            Reporter: Shalin Shekhar Mangar
>            Priority: Major
>
> Rebalance leaders API requires that nodes be set with preferredLeaders property. But in theory this is not required. We can choose replicas on unique nodes to be leaders in the absence of the preferredLeader property.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org