[
https://issues.apache.org/jira/browse/SOLR-10656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005007#comment-16005007
]
Victor Igumnov commented on SOLR-10656:
---------------------------------------
Looks like Solr 6.5.x defaults to true for the legacyCloud option if not
defined. Thank you for the hint on tracking it down.
https://github.com/apache/lucene-solr/blob/branch_6_5/solr/core/src/java/org/apache/solr/cloud/Overseer.java#L760
This issue can be closed, just unexpected behavior.
> Collection re-registering after deletion
> ----------------------------------------
>
> Key: SOLR-10656
> URL: https://issues.apache.org/jira/browse/SOLR-10656
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 6.5.1
> Environment: Linux / Ubuntu
> Reporter: Victor Igumnov
> Labels: bug
>
> Taking a single node down in a multi-node solr cloud cluster and then issuing
> a delete collection command will succeed with a HTTP 200. The collection will
> be removed from ZK and the data files removed from the active nodes. Once the
> downed node is brought back into the cluster the deleted collection
> re-registers it self with zookeeper and is actively queryable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
