[ https://issues.apache.org/jira/browse/SOLR-10704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrzej Bialecki reassigned SOLR-10704: ---------------------------------------- Assignee: Andrzej Bialecki > REPLACENODE can make the collection lost data which replicaFactor is 1 > ----------------------------------------------------------------------- > > Key: SOLR-10704 > URL: https://issues.apache.org/jira/browse/SOLR-10704 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: SolrCloud > Affects Versions: 6.2 > Environment: Red Hat 4.8.3-9, JDK 1.8.0_121 > Reporter: Daisy.Yuan > Assignee: Andrzej Bialecki > Attachments: 219.log > > > 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) -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org