[
https://issues.apache.org/jira/browse/SOLR-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049846#comment-15049846
]
Mark Miller commented on SOLR-8368:
-----------------------------------
So one thing to note is that the leader election peersync does not currently
set starting versions. So it's using a fresh recent versions call. Though I
suppose all of should be using uncapped tlogs?
I'm still seeing a 4.10.3 + backports version of Solr that has had a non clean
shutdown, comes back up, and it tries to become leader with versions much older
than what it has sent its replicas (and we add locally before sending to
replicas at all). And they are about the length of a hard autocommit (60s)
older.
> A SolrCore needs to replay it's tlog before the leader election process.
> ------------------------------------------------------------------------
>
> Key: SOLR-8368
> URL: https://issues.apache.org/jira/browse/SOLR-8368
> Project: Solr
> Issue Type: Bug
> Reporter: Mark Miller
> Assignee: Mark Miller
> Attachments: SOLR-8368.patch
>
>
> If we do it after like now, the correct leader may not be able to become
> leader.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
