[
https://issues.apache.org/jira/browse/SOLR-16403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600939#comment-17600939
]
David Smiley commented on SOLR-16403:
-------------------------------------
Possible issues:
* ensuring that requests-in-progress can complete without interruption
(assuming they don't take _too_ long)
* ensuring that CloudSolrClient is smart enough to recognize a 404 means it may
simply have an out-dated cluster state. It should try to get the state again,
and if it changed, issue the request one last time before propagating the error.
Some tests with concurrent load can tease out issues in the above.
> 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]
