lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cao Manh Dat (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-11011) Assign.buildCoreName can lead to error in creating a new core when legacyCloud=false
Date Wed, 05 Jul 2017 15:22:00 GMT

     [ https://issues.apache.org/jira/browse/SOLR-11011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Cao Manh Dat updated SOLR-11011:
--------------------------------
    Description: 
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.

  was:
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, it lead to a failure.


> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message