[jira] [Commented] (SOLR-10285) Skip LEADER messages when there are leader only shards

["David Smiley (Jira)" <ji...@apache.org>]

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

David Smiley commented on SOLR-10285:
-------------------------------------

FYI my colleague [~pierre.salagnac] observed that this optimization can be faulty when the leader looses the status and becomes the leader again (no other leader in the meantime).  May require the Overseer to be very busy.  It'd be better to optimize avoiding recovery status instead of leadership.

> Skip LEADER messages when there are leader only shards
> ------------------------------------------------------
>
>                 Key: SOLR-10285
>                 URL: https://issues.apache.org/jira/browse/SOLR-10285
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Varun Thacker
>            Assignee: Cao Manh Dat
>            Priority: Major
>             Fix For: 7.1, 8.0
>
>         Attachments: SOLR-10285.patch, SOLR-10285.patch, SOLR-10285.patch
>
>
> For shards which have 1 replica ( leader ) we know it doesn't need to recover from anyone. We should short-circuit the recovery process in this case. 
> The motivation for this being that we will generate less state events and be able to mark these replicas as active again without it needing to go into 'recovering' state. 
> We already short circuit when you set {{-Dsolrcloud.skip.autorecovery=true}} but that sys prop was meant for tests only. Extending this to make sure the code short-circuits when the core knows its the only replica in the shard is the motivation of the Jira.



--
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