[ https://issues.apache.org/jira/browse/SOLR-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261246#comment-14261246 ]
Ramkumar Aiyengar commented on SOLR-5209: ----------------------------------------- I think this might fail {{BasicDistributedZkTest.testFailedCoreCreateCleansUp}}.. If we call core create, it happens to be the first core of the collection, and the core creation fails (due to say, a config issue) -- the test currently verifies if the rollback happens by checking for the absence of the collection. We could obviously change the test, but in such a case, should we be removing the collection as well? (or disallow creation of a core for a non-existent collection -- though that might be a bigger, disruptive end user change and not necessarily good).. > last replica removal cascades to remove 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org