[ https://issues.apache.org/jira/browse/SOLR-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Neulinger updated SOLR-5665: ----------------------------------- Attachment: recreate-solr-cores.pl simple example perl script to do it as an example of how trivial it is. > Would like a 'REBUILD' method in the collections api to reconstruct missing > cores > --------------------------------------------------------------------------------- > > Key: SOLR-5665 > URL: https://issues.apache.org/jira/browse/SOLR-5665 > Project: Solr > Issue Type: New Feature > Components: SolrCloud > Reporter: Nathan Neulinger > Attachments: recreate-solr-cores.pl > > > Test Scenario: > Multinode solrCloud deployment > Completely delete one of those nodes > Bring it back online empty (no cores, no indexes at all) > Node will come up with each of the replicas in recovery mode and they will > stay there forever since the cores don't actually exist. > I've written a small external script that goes and gets the > collections/shards/replicas->core mapping from clusterstate.json, and then > calls the core create url for each core that is in a down state. This was > relatively easy to implement externally - and should be even more trivial to > implement inside of the collections api. > I envision this to apply this to all collections: > http://localhost:8983/solr/admin/collections?action=REBUILD > and this to apply the operation to a single collection: > http://localhost:8983/solr/admin/collections?action=REBUILD&name=collname > Independently, I'd like to see this sort of "server is blank, recreate > missing automatically" triggered automatically, but I can see where that > might not be expected behavior. -- This message was sent by Atlassian JIRA (v6.1.5#6160) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org