[
https://issues.apache.org/jira/browse/SOLR-18080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18068061#comment-18068061
]
ASF subversion and git services commented on SOLR-18080:
--------------------------------------------------------
Commit 9878ad54b03ceb2b56e20961a1e66beffdd436db in solr's branch
refs/heads/branch_10x from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=9878ad54b03 ]
SOLR-18080: Initiate Leader election for ShardTerms (#4069)
(cherry picked from commit a364ac71b8392251bc2b10abfb6ff5b3b927135c)
> Changes in ShardTerms should be able to trigger leader election
> ---------------------------------------------------------------
>
> Key: SOLR-18080
> URL: https://issues.apache.org/jira/browse/SOLR-18080
> Project: Solr
> Issue Type: Improvement
> Reporter: Houston Putman
> Assignee: Houston Putman
> Priority: Major
> Labels: pull-request-available
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> Currently ShardTerms aid in doing Leader-initiated-recovery (LIR) during
> indexing for Solr shards/replicas. However other parts of Solr do modify the
> Shard terms, and the replicas should handle these changes gracefully.
> One of these changes is the leader having a shard term lower than other
> replicas in the shard. In this case it should give up leadership, and a
> leader-election should take place.
> This would be helpful in places like InstallShardData or RestoreCollection,
> where non-leader replicas may have more up-to-date versions of the index than
> the leader.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
