[
https://issues.apache.org/jira/browse/SOLR-16403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600944#comment-17600944
]
Gus Heck commented on SOLR-16403:
---------------------------------
My vague recollection/feeling is that this didn't delete the original in case
there was a problem resulting from the split. Might problems be discovered say
if someone realizes after the split that there were usages of graph query that
wanted documents co-located (I can't recall OTTOMH if it cares about same
shard, or just that shards are on the same machine, but that's just a quick
hypothetical)?
Certainly an option to auto clean sounds good, but not sure it should be the
default (but also not sure it shouldn't be other than the obvious back
compatibility issue).
> 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
>
> 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]
