[
https://issues.apache.org/jira/browse/SOLR-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049798#comment-15049798
]
Mark Miller commented on SOLR-8368:
-----------------------------------
It's going to pull from the uncapped log?
In the incident that brought this to attention, an uncapped log was not yet
replayed, and when the leader attempted to peer sync with its replica(s) it was
using versions from before the last hard commit it appeared, rather than what
was in the uncapped tlog. The only explanation I can think of for seeing this
is the uncapped tlog disappeared or the leader election peer sync process was
not using updates from that uncapped log.
> 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]
