[ https://issues.apache.org/jira/browse/SOLR-11011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075934#comment-16075934 ]
Shalin Shekhar Mangar commented on SOLR-11011: ---------------------------------------------- Nice Dat! Although this was caught while testing {{autoAddReplicasPlanAction}} for autoscaling, it can happen today in the wild if a user uses the DELETEREPLICA or MOVEREPLICA or REPLACENODE API to delete replicas and then a new replica is created on the same node with the same core name. > Assign.buildCoreName can lead to error in creating a new core when > legacyCloud=false > ------------------------------------------------------------------------------------ > > Key: SOLR-11011 > URL: https://issues.apache.org/jira/browse/SOLR-11011 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Reporter: Cao Manh Dat > Assignee: Cao Manh Dat > > Here are the case > {code} > shard1 : { > node1 : shard1_replica1, > node2 : shard1_replica2 > } > {code} > node2 go down, autoAddReplicasPlanAction is executed > {code} > shard1 : { > node1 : shard1_replica1, > node3 : shard1_replica3 > } > {code} > node2 back alive, because shard1_replica2 is removed from {{states.json}} so > that core won't be loaded ( but it won't be removed neither ). Then node1 go > down, Assign.buildCoreName will create a core with name=shard1_replica2 which > lead to a failure. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org