[
https://issues.apache.org/jira/browse/SOLR-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105826#comment-17105826
]
Ilan Ginzburg commented on SOLR-12823:
--------------------------------------
[~janhoy], [~ab], the autoscaling simulation framework
(org.apache.solr.cloud.autoscaling.sim) blocks clean removal of stateFormat=1
collections and associated management of /clusterstate.json in the Overseer...
It currently only supports the old state format.
Having it create "stateFormat=2" collections (quotes because I'm removing the
stateFormat concept altogether) having each its own state.json shouldn't be a
big deal, but I'm not familiar with how it's used to understand the
consequences of the absence of a single state ZK file.
Also, the concept of a global config "version" (mapping to a znode version) no
longer exists with per collection state.json and unfortunately the sim code
seems to rely on it quite a bit.
I need some guidance on the best way to deal with this here, thanks.
> remove clusterstate.json in Lucene/Solr 8.0
> -------------------------------------------
>
> Key: SOLR-12823
> URL: https://issues.apache.org/jira/browse/SOLR-12823
> Project: Solr
> Issue Type: Task
> Reporter: Varun Thacker
> Priority: Major
>
> clusterstate.json is an artifact of a pre 5.0 Solr release. We should remove
> that in 8.0
> It stays empty unless you explicitly ask to create the collection with the
> old "stateFormat" and there is no reason for one to create a collection with
> the old stateFormat.
> We should also remove the "stateFormat" argument in create collection
> We should also remove MIGRATESTATEVERSION as well
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]