Shawn Heisey created SOLR-13396:
-----------------------------------
Summary: SolrCloud will delete the core data for any core that is
not referenced in the clusterstate
Key: SOLR-13396
URL: https://issues.apache.org/jira/browse/SOLR-13396
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: SolrCloud
Affects Versions: 8.0, 7.3.1
Reporter: Shawn Heisey
SOLR-12066 is an improvement designed to delete core data for replicas that
were deleted while the node was down -- better cleanup.
In practice, that change causes SolrCloud to delete all core data for cores
that are not referenced in the ZK clusterstate. If all the ZK data gets
deleted or the Solr instance is pointed at a ZK ensemble with no data, it will
proceed to delete all of the cores in the solr home, with no possibility of
recovery.
I do not think that Solr should ever delete core data unless an explicit DELETE
action has been made and the node is operational at the time of the request.
If a core exists during startup that cannot be found in the ZK clusterstate, it
should be ignored (not started) and a helpful message should be logged. I
think that message should probably be at WARN so that it shows up in the admin
UI logging tab with default settings.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
