[jira] [Commented] (SOLR-5209) cores/action=UNLOAD of last replica removes shard from clusterstate

["Ramkumar Aiyengar (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237820#comment-14237820 ] 

Ramkumar Aiyengar commented on SOLR-5209:
-----------------------------------------

This seems to be still relevant (in SliceMutator though rather than Overseer after the refactoring), 5.0 might be a good time to revisit this behaviour since the concerns above were more of back-compat..

> cores/action=UNLOAD of last replica removes shard from clusterstate
> -------------------------------------------------------------------
>
>                 Key: SOLR-5209
>                 URL: https://issues.apache.org/jira/browse/SOLR-5209
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.4
>            Reporter: Christine Poerschke
>            Assignee: Mark Miller
>         Attachments: SOLR-5209.patch
>
>
> The problem we saw was that unloading of an only replica of a shard deleted that shard's info from the clusterstate. Once it was gone then there was no easy way to re-create the shard (other than dropping and re-creating the whole collection's state).
> This seems like a bug?
> Overseer.java around line 600 has a comment and commented out code:
> // TODO TODO TODO!!! if there are no replicas left for the slice, and the slice has no hash range, remove it
> // if (newReplicas.size() == 0 && slice.getRange() == null) {
> // if there are no replicas left for the slice remove it



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org