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

Shalin Shekhar Mangar commented on SOLR-6420:
---------------------------------------------

The only reason I can think when such a problem will happen is if Lucene/Solr 
lied about the current index generation/version (returned 0 for both) and Solr 
thinks that the replication actually succeeded. We don't guarantee anything 
when you're running unreleased code and there's no way for me to verify/fix 
this bug in the absence of the exact bits you deployed and your index files and 
even then it probably won't be a high priority (I'd rather fix bugs that we've 
released).

> ADDREPLICA can add a replica that reports green without actually replicating
> ----------------------------------------------------------------------------
>
>                 Key: SOLR-6420
>                 URL: https://issues.apache.org/jira/browse/SOLR-6420
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.10
>         Environment: Ubuntu 14.04
>            Reporter: Ralph Tice
>            Priority: Critical
>              Labels: SolrCloud, difficulty-medium, impact-high
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> I am running Solr built off branch_4x, and thanks to some help from IRC 
> ([[email protected]]) we've determined that we have an incompatible 
> index situation where we have indexes built with 4.9 that we can read but not 
> index into further or update.  In this situation, if I try to add a replica, 
> this also fails, however, the only log ouput (at WARN threshold) is:
>    16:21:58.156 [RecoveryThread] WARN  org.apache.solr.update.PeerSync - no 
> frame of reference to tell if we've missed updates
>  ...and the replica comes up green.  I think this might indicate a missing 
> integrity check on replication but certainly IMO a replica should report as 
> green/active if it is not on the same revision as the leader, or at least if 
> it has never been on the same revision as the leader.
> Shards built with the currently running version of Solr are able to 
> successfully ADDREPLICA as expected.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to