[
https://issues.apache.org/jira/browse/SOLR-11011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099678#comment-16099678
]
ASF subversion and git services commented on SOLR-11011:
--------------------------------------------------------
Commit f087c5acae1b1a62b75f4d0caac660088f03ed35 in lucene-solr's branch
refs/heads/master from [~caomanhdat]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f087c5a ]
SOLR-11011: Fix backward compatibility problem + audit the usage of old
Assign.buildCoreName(String collectionName, String shard, Replica.Type type,
int replicaNum)
> 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
> Fix For: master (8.0), 7.1
>
> Attachments: SOLR-11011.2.patch, SOLR-11011.2.patch,
> SOLR-11011.patch, SOLR-11011.patch, SOLR-11011.patch, SOLR-11011.patch
>
>
> 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
