[
https://issues.apache.org/jira/browse/SOLR-16403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827314#comment-17827314
]
ASF subversion and git services commented on SOLR-16403:
--------------------------------------------------------
Commit 4098d6ae3e298efdfa219d5a2629d69f60c5aff9 in solr's branch
refs/heads/branch_9x from pjmcarthur
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=4098d6ae3e2 ]
SOLR-16403: ClusterSingleton to remove inactive Shards (#1926)
ClusterSingleton that periodically removes state=INACTIVE shards. These occur
from shard splits.
Co-authored-by: Paul McArthur <pmcarthur-apa...@proton.me>
(cherry picked from commit ca58f1aa90b351b69b0ec4184adbaaca03978573)
> 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: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
