[
https://issues.apache.org/jira/browse/SOLR-16403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828602#comment-17828602
]
ASF subversion and git services commented on SOLR-16403:
--------------------------------------------------------
Commit 75e8de64fabe1b96cc262b85220ecc91ffcad49d in solr's branch
refs/heads/branch_9x from pjmcarthur
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=75e8de64fab ]
SOLR-16403: Fix DeleteShardTest (#2359)
Simple mistake; test failed sometimes
Co-authored-by: Paul McArthur <[email protected]>
(cherry picked from commit f56db508e25035309e58e60e75ecbc5ac75ef278)
> 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
> Fix For: 9.6.0
>
> 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]