David Smiley created SOLR-12308:
-----------------------------------
Summary: LISTALIASES should return up to date response
Key: SOLR-12308
URL: https://issues.apache.org/jira/browse/SOLR-12308
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Components: SolrCloud
Reporter: David Smiley
Assignee: David Smiley
The LISTALIASES command might return a stale response due to the default
eventual consistency of reads of ZooKeeper. I think if someone calls this
command (which generally won't be rapid-fire), they deserve an up to date
response. This is easily done with a one-liner; patch forthcoming.
Returning stale alias info is the only plausible explanation I have for why a
recent CI failure for AliasesIntegrationTest.tearDown() failed to detect
aliases to be deleted. It calls listAliases to know which aliases exist so it
can then delete them 1st.
[https://jenkins.thetaphi.de/job/Lucene-Solr-master-Solaris/1833/]
tearDown then calls MiniSolrCloudCluster.deleteAllCollections() which
interestingly grabs a ZkStateReader.createClusterStateWatchersAndUpdate()....
perhaps this ought to delete all aliases _as well_ since, after all, if there
were any aliases then well deleting all collections is bound to fail. Should I
file a separate issue or just handle this together?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
