lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <>
Subject [jira] [Commented] (SOLR-7389) Expose znode version in clusterstatus API
Date Mon, 25 May 2015 14:53:17 GMT


Shalin Shekhar Mangar commented on SOLR-7389:

Thanks [~mariusneo] but this is patch isn't quite right. The DocCollection#write method is
used to persist the collection information to ZK but we don't want znodeVersion to be persisted
to ZK as part of the collection. It is best to add the znodeVersion manually to the collection
information being returned by the cluster status API. Look at OverseerCollectionProcessor#getClusterStatus
where this is all done. Also, all tests for this API are in TestCollectionAPI so I'd appreciate
if you can add a test for this new feature as well.

> Expose znode version in clusterstatus API
> -----------------------------------------
>                 Key: SOLR-7389
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>            Reporter: Shalin Shekhar Mangar
>            Assignee: Shalin Shekhar Mangar
>            Priority: Minor
>              Labels: difficulty-easy, impact-medium
>             Fix For: Trunk, 5.2
>         Attachments: SOLR-7389.patch
> We should expose the znode version of the cluster state for each collection that is returned
by the clusterstatus API.
> Apart from giving an idea about when the clusterstatus was executed, this information
can be used by non-java clients to use the same _stateVer_ mechanism that SolrJ currently
uses for routing requests without watching all cluster states.

This message was sent by Atlassian JIRA

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

View raw message