[SOLR-11011] Assign.buildCoreName can lead to error in creating a new core when legacyCloud=false

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 7.1, 8.0
• Assignee: Cao Manh Dat
• Reporter: Cao Manh Dat
• Created: 05/Jul/17 15:20
• Updated: 02/Oct/19 17:24
• Resolved: 18/Sep/17 23:06

Description

Here are the case

shard1 : {
    node1 : shard1_replica1,
    node2 : shard1_replica2
}

node2 go down, autoAddReplicasPlanAction is executed

shard1 : {
    node1 : shard1_replica1,
    node3 : shard1_replica3
}

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.

Issue Links

• blocks: SOLR-10397 Port 'autoAddReplicas' feature to the autoscaling framework and make it work with non-shared filesystems