lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gus Heck (JIRA)" <>
Subject [jira] [Commented] (SOLR-12308) LISTALIASES should return up to date response
Date Mon, 07 May 2018 23:11:00 GMT


Gus Heck commented on SOLR-12308:

Changes all look good to me :)

> LISTALIASES should return up to date response
> ---------------------------------------------
>                 Key: SOLR-12308
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>            Reporter: David Smiley
>            Assignee: David Smiley
>            Priority: Minor
>         Attachments: SOLR-12308.patch
> 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.
>  []
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message