lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <>
Subject [jira] [Updated] (SOLR-6420) ADDREPLICA can add a replica that reports green without actually replicating
Date Mon, 01 Sep 2014 21:10:20 GMT


Shalin Shekhar Mangar updated SOLR-6420:
                Labels: SolrCloud difficulty-medium impact-high  (was: )
    Remaining Estimate: 96h
     Original Estimate: 96h

> ADDREPLICA can add a replica that reports green without actually replicating
> ----------------------------------------------------------------------------
>                 Key: SOLR-6420
>                 URL:
>             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 ([])
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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message