[ 
https://issues.apache.org/jira/browse/SOLR-14648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17157579#comment-17157579
 ] 

Erick Erickson edited comment on SOLR-14648 at 7/14/20, 7:01 PM:
-----------------------------------------------------------------

(2) seems safer, assuming that the TLOG replica never gets created without the 
special flag. Maybe the expert flag would be the PULL replica to grab the index 
from?

(1) seems trickier. It'd have to be generalized to _never_ become the leader, 
even if the cluster was restarted afterwards. Having a TLOG replica 
successfully created seems like it'd have more places to go wrong. Also, how 
would the cluster get out of that state? You'd have to do something like 
FORCELEADER which would have some of the same problems...

 

Hmmmm, or would the ability to "promote" a replica from PULL to TLOG work?


was (Author: erickerickson):
(2) seems safer, assuming that the TLOG replica never gets created without the 
special flag. Maybe the expert flag would be the PULL replica to grab the index 
from?

(1) seems trickier. It'd have to be generalized to _never_ become the leader, 
even if the cluster was restarted afterwards. Having a TLOG replica 
successfully created seems like it'd have more places to go wrong. Also, how 
would the cluster get out of that state? You'd have to do something like 
FORCELEADER which would have some of the same problems...

> 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

Reply via email to