[
https://issues.apache.org/jira/browse/SOLR-16403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-16403:
--------------------------------
Description:
Have a periodic mechanism to delete state=INACTIVE shards. The implementation
is a ClusterSingleton.
----
*Original title:* SPLITSHARD should delete the parent shard after success
*Original description: *
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.
was: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.
> INACTIVE shards should be deleted periodically
> ----------------------------------------------
>
> Key: SOLR-16403
> URL: https://issues.apache.org/jira/browse/SOLR-16403
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: David Smiley
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Have a periodic mechanism to delete state=INACTIVE shards. The
> implementation is a ClusterSingleton.
> ----
> *Original title:* SPLITSHARD should delete the parent shard after success
> *Original description: *
> 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]
