[
https://issues.apache.org/jira/browse/SOLR-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060299#comment-15060299
]
Erick Erickson commented on SOLR-8423:
--------------------------------------
I don't think this breaks back-compat 'cause I don't see any promises in the
docs ;) But I vaguely recall that this was to clean up stale cluster states
without having to directly edit the ZK node, so maybe nobody thought about it?
I might advocate an option to keep at least the data directory just on general
principles here though. I'm thinking of the case where the user is explicitly
controlling routing, say time-series data. Does it make sense to delete/create
shards to hide/show some time-interval? I have to admit this is a _theoretical_
use-case, haven't seen anyone actually ask for it so feel free to ignore...
> DELETESHARD should cleanup the instance and data directory, like DELETEREPLICA
> ------------------------------------------------------------------------------
>
> Key: SOLR-8423
> URL: https://issues.apache.org/jira/browse/SOLR-8423
> Project: Solr
> Issue Type: Bug
> Reporter: Anshum Gupta
>
> DELETESHARD only cleans up the index directory and not the instance/data
> directory. DELETEREPLICA on the other hand cleans up the data and instance
> directory.
> DELETESHARD should clean up the instance and data directory, so that we don't
> leak disk space on executing the command.
> If we think this would break back-compat, though I don't see why this should
> not clean up the instance dir, we should at least provide an option to clean
> up everything and make it default in 6.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
