Mark, I appreciate all the context. ...
Mark Miller-3 wrote > What do you mean you are hosed? > > All the SolrCores should be gone, so why does it matter so much that the > collection is gone? In the days before the collections api, if you wanted > to then create the collection again, just create a solrcore, same way a > collection was created initially. > > Without the zk=cluster_truth mode, we have to support both collections api > collections, and pre configured implicit collections, created and removed > via SolrCores. You're hosed most especially because clusterstate.json loses knowledge of what the hash range is for the shard (and everything else) once there are no more replicas for the shard. I'm not trying to delete the collection, I'm trying to *replace* the replicas of the shards of the collection. My experiment was to unload the replicas (of just one shard; the others would be handled later) but before I could get to adding a backed-up replica I observed clusterstate.json lost all knowledge of what that shard was and then I realize I was hosed. But any way, this simply isn't going to work for the reasons you gave. I'm hoping for some way to clone or reconstitute a collection from a backup. I can manually create the collection similar to how it was created the first time, but after shard-splitting I fear that isn't feasible since the backups won't align with the new collection's shard hash ranges unless I can specify what those hash-ranges are (but I can't). Maybe manual clusterstate.json surgery is inevitable. This is what I raised in the other email I sent at a similar time to the one your replied to. ~ David ----- Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book -- View this message in context: http://lucene.472066.n3.nabble.com/Removing-last-replica-from-a-SolrCloud-collection-tp4114772p4114905.html Sent from the Solr - User mailing list archive at Nabble.com.
