[
https://issues.apache.org/jira/browse/SOLR-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17109682#comment-17109682
]
Ilan Ginzburg commented on SOLR-12823:
--------------------------------------
When {{/clusterstate.json}} is not empty Solr should not start.
In that an ERROR log is issued, but the system doesn't nicely stop the startup
process. From the {{bin/solr start}} command line things even look ok.
The check got added as soon as there's a connection to ZK, in the
{{ZkController}} constructor after {{zkClient}} is built. It throws a
{{SolrException}} (or {{ZooKeeperException}}, same behavior) if it's unhappy.
Is there a nicer (yet more drastic) way to give up at this stage rather than
leaving the system in a broken state? (UI Admin returns "HTTP ERROR 404
javax.servlet.UnavailableException: Error processing the request. CoreContainer
is either not initialized or shutting down.")
I know this will not happen very often and if it does by looking at the logs
the user will quickly figure it out, but if things can be made more friendly...
> 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]