[
https://issues.apache.org/jira/browse/SOLR-16403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17601118#comment-17601118
]
David Smiley commented on SOLR-16403:
-------------------------------------
Changing the default behavior for Solr 10 would make sense.
> SPLITSHARD should delete the parent shard after success
> -------------------------------------------------------
>
> Key: SOLR-16403
> URL: https://issues.apache.org/jira/browse/SOLR-16403
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: David Smiley
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When a shard is split into two sub-shards, the parent (the original) will
> remain in an "INACTIVE" state. It's up to the user/admin to devise some
> clean-up process. I propose that SplitShardCmd clean up after itself. It's
> not clear why it didn't do this all along.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
