[
https://issues.apache.org/jira/browse/SOLR-14648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17157456#comment-17157456
]
Ishan Chattopadhyaya commented on SOLR-14648:
---------------------------------------------
Agree, Erick. This will result in a data loss.
I propose we fix this as:
When a TLOG replica comes up and sees there are no other TLOG/NRT replicas to
replicate from, either
# TLOG replica doesn't become a leader, since it is behind the PULL replicas.
This will stop the scary situation where it becomes leader with empty index.
# Or, when the ADDREPLICA command contains some special expert level flag, it
replicas from the PULL replica (with the full knowledge that there will be a
data loss situation).
WDYT, [~sayan.das], [~erickerickson]?
> Creating TLOG with pure multiple PULL replica, leading to 0 doc count
> ---------------------------------------------------------------------
>
> Key: SOLR-14648
> URL: https://issues.apache.org/jira/browse/SOLR-14648
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 8.3.1
> Reporter: Sayan Das
> Priority: Major
>
> With only PULL replica whenever we create a new TLOG as leader fresh
> replication happens, resulting in flushing the older indexes from existing
> PULL replicas
> Steps to replicate:
> # Create 1 NRT or 1 TLOG replica as leader with multiple PULL replicas
> # Index few documents and let it replicate in all the replicas
> # Delete all the TLOG/NRT replica leaving PULL types
> # Create a new TLOG/NRT as leader, once recovery completes it replaces all
> the older indexes
> In ideal scenario it should have replicated from any one of the PULL replicas
> that has latest indexes after that TLOG/NRT replica should be registered as
> leader
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
