You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mano Kovacs (JIRA)" <ji...@apache.org> on 2017/10/04 09:55:00 UTC

[jira] [Commented] (SOLR-11435) Replicas failed to be deleted can overwrite replicas of recreated collections

    [ https://issues.apache.org/jira/browse/SOLR-11435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191072#comment-16191072 ] 

Mano Kovacs commented on SOLR-11435:
------------------------------------

CC: [~varunthacker], [~markrmiller@gmail.com]

> Replicas failed to be deleted can overwrite replicas of recreated collections
> -----------------------------------------------------------------------------
>
>                 Key: SOLR-11435
>                 URL: https://issues.apache.org/jira/browse/SOLR-11435
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 7.0
>            Reporter: Mano Kovacs
>
> When a replica comes up that was deleted from ZK while it was gone, it can replace replicas in ZK if the collection an core names are equal.
> Reproduction:
> # Create {{collection1}} with 1 shard, 2 replicas on {{node1}} and {{node2}}
> # Shut down {{node2}}
> # Delete {{collection1}}
> # Create {{collection1}} on {{node1}} and {{node3}}
> # Start {{node2}}
> Expected:
> {{node2}} will not initialize node as it is not assigned to in ZK ({{legacyCloud=false}})
> Actual:
> {{node2}} will overwrite the {{baseurl}} in {{state.json}} for one of the replicas as the {{coreNodeName}} and the collection name will match the core it has.
> Note: SOLR-7248 introduced a {{baseurl}} comparison which was removed in SOLR-10279.



--
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