[ 
https://issues.apache.org/jira/browse/SOLR-16438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696104#comment-17696104
 ] 

ASF subversion and git services commented on SOLR-16438:
--------------------------------------------------------

Commit cf822cf5f8081efa3b7f53822be7828967012680 in solr's branch 
refs/heads/main from Bruno Roustant
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=cf822cf5f80 ]

Revert "SOLR-16438: Support optional split.setPreferredLeaders prop in shard 
split command."

This reverts commit fae42ec0cf43f288c909cb2e12b4d68e6a409d33.
This reverts commit 57e73e4f9066712a16b0885b0db2482ec106bfb9.
This reverts commit 0051ecf1f81927cfb1f6c54935a19ea521b616ba.


> Shard split should be able to set preferred leaders on other replicas
> ---------------------------------------------------------------------
>
>                 Key: SOLR-16438
>                 URL: https://issues.apache.org/jira/browse/SOLR-16438
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Bruno Roustant
>            Assignee: Bruno Roustant
>            Priority: Major
>             Fix For: 9.2
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Currently, shard split always create a first replica for each sub-shard on 
> the current host. Then it creates other replicas and their corresponding 
> sub-shards are in RECOVERY state. The effect is that the first replica (on 
> the current host) is always the leader, meaning that if the sub-shards are 
> split themselves, their sub-sub-shards leaders are also on the same host.
> This can lead to very unbalanced situation where the same host is the leader 
> for a whole set of shards.
> A solution to distribute evenly the leaders is to flag some other replicas 
> with the preferredLeader property during the split. Then a rebalance-leaders 
> command can elect the appropriate leaders. If we do that for each split, then 
> all the sub-shards have their leaders correctly balanced.
> To go further, we can improve CollectionsHandler#CollectionOperation to 
> support combined operations. That way a CollectionOperation#SPLITSHARD_OP can 
> trigger a split op, then a wait for split completion op, and then a rebalance 
> leaders op.



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

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

Reply via email to