lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Koen De Groote (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-13396) SolrCloud will delete the core data for any core that is not referenced in the clusterstate
Date Fri, 12 Apr 2019 08:01:00 GMT

    [ https://issues.apache.org/jira/browse/SOLR-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816063#comment-16816063
] 

Koen De Groote commented on SOLR-13396:
---------------------------------------

Just going to add this link to the mail archive where the question was asked: [https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201904.mbox/%3CCAPPyzbwMr1EN97h-TnsebAgw6pL8i8GNa41zE7Q6ksvqkAnqLA%40mail.gmail.com%3E]

In case someone wants the reference.

> 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: 7.3.1, 8.0
>            Reporter: Shawn Heisey
>            Priority: Major
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message