[
https://issues.apache.org/jira/browse/SOLR-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105542#comment-17105542
]
Jan Høydahl commented on SOLR-12823:
------------------------------------
[~murblanc] volunteered on mailing list to try a PR. I have not looked into
this in detail. You should consult
[https://lucene.apache.org/solr/guide/8_5/cluster-node-management.html#migratestateformat]
and the code of course to understand this move. But this could be an approach:
* In 8.6 do at least this
## print a big WARNING if clusterstate.json is used for a collection, telling
user to migrate
## OR auto migrate all collections on overseer startup? Is it safe?
* In 9.0 (master), do at least this:
## Add migration note to RefGuide, telling users to run MIGRATESTATEFORMAT for
all collections before upgrading
## remove parsing of and support for clusterstate.json in Overseer
## Perhaps add a check in Overseer and if the old znode exists and is
non-empty, print an ERROR and abort?
## If clusterstatus.json exists and is empty, remove it and print a log
> 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: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
