[
https://issues.apache.org/jira/browse/SOLR-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000967#comment-16000967
]
Joshua Humphries commented on SOLR-10285:
-----------------------------------------
[~dragonsinth], I'm afraid I don't have a patch. I do have a branch where I
made a lot of progress, but I did not finish getting unit tests to pass. The
patch for SOLR-10277 ended up being sufficient for our restart-time objectives
at the time, so I put it on the back-burner. This change would certainly reduce
the restart time further, quite considerably, in fact, for deployments with a
large number of shards that do not have multiple replicas. I'll dust it off
today and try to assess remaining work to get it merge-worthy.
> Reduce state messages when there are leader only shards
> -------------------------------------------------------
>
> Key: SOLR-10285
> URL: https://issues.apache.org/jira/browse/SOLR-10285
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Varun Thacker
> Assignee: Cao Manh Dat
>
> 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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
