You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Cao Manh Dat (JIRA)" <ji...@apache.org> on 2017/10/04 02:01:01 UTC
[jira] [Closed] (SOLR-10285) Skip LEADER messages when there are
leader only shards
[ https://issues.apache.org/jira/browse/SOLR-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cao Manh Dat closed SOLR-10285.
-------------------------------
Resolution: Fixed
> 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
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Varun Thacker
> Assignee: Cao Manh Dat
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org