Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-10704

REPLACENODE can make the collection lost data which replicaFactor is 1

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.2
    • Fix Version/s: 6.7, 7.0
    • Component/s: SolrCloud
    • Security Level: Public (Default Security Level. Issues are Public)
    • Labels:
      None
    • Environment:

      Red Hat 4.8.3-9, JDK 1.8.0_121

      Description

      When some replicas which the relative collection's replicaFactor is 1, it will lost data after executing the REPLACENODE cmd.

      It may be the new replica on the target node does not complete revovering, but the old replica on the source node was already be deleted.

      At last the target revocery failed for the following exception:
      2017-05-18 17:08:48,587 | ERROR | recoveryExecutor-3-thread-2-processing-n:192.168.229.137:21103_solr x:replace-hdfs-coll1_shard1_replica2 s:shard1 c:replace-hdfs-coll1 r:core_node3 | Error while trying to recover. core=replace-hdfs-coll1_shard1_replica2:java.lang.NullPointerException
      at org.apache.solr.update.PeerSync.alreadyInSync(PeerSync.java:339)

        Attachments

        1. 219.log
          9 kB
          Daisy.Yuan
        2. SOLR-10704.patch
          9 kB
          Andrzej Bialecki
        3. SOLR-10704.patch
          8 kB
          Andrzej Bialecki

          Activity

            People

            • Assignee:
              ab Andrzej Bialecki
              Reporter:
              daisy_yu Daisy.Yuan
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: