You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2018/04/23 20:52:00 UTC
[jira] [Created] (SOLR-12261) Deleting collections should sync
aliases before prematurely failing when alias is deleted
David Smiley created SOLR-12261:
-----------------------------------
Summary: Deleting collections should sync aliases before prematurely failing when alias is deleted
Key: SOLR-12261
URL: https://issues.apache.org/jira/browse/SOLR-12261
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: SolrCloud
Reporter: David Smiley
Assignee: David Smiley
In SOLR-11218 [~erickerickson] ensured that we can't delete a collection that is referenced by an alias. However It may be that the alias is deleted but the node servicing the request doesn't know about this yet. It should call AliasesManager.update() first (which now sync()'s with ZK).
I believe this is the cause of some sporadic failures to org.apache.solr.cloud.AliasIntegrationTest#tearDown which deletes the alias then all collections.
It's debatable if this is an improvement or a bug. Sadly most of SolrCloud simply seems to operate this way despite it being eventually consistent. Thus users using SolrCloud may have to add sleep()s after calls to Solr adminĀ callsĀ :-/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org