You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/06/29 10:18:00 UTC
[jira] [Commented] (SOLR-13396) SolrCloud will delete the core data for any core that is not referenced in the clusterstate
[ https://issues.apache.org/jira/browse/SOLR-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738470#comment-17738470 ]
ASF subversion and git services commented on SOLR-13396:
--------------------------------------------------------
Commit c8ee862b7a8c39b3ee9f43fbdcee80799d56f3df in solr's branch refs/heads/main from Colvin Cowie
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=c8ee862b7a8 ]
SOLR-13396 - Disable deletion of unknown cores by default (#1321)
Previous behavior is now disabled by default, set -Dsolr.deleteUnknownCores=true to use the old behavior.
> 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
> Components: SolrCloud
> Affects Versions: 7.3.1, 8.0
> Reporter: Shawn Heisey
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org