I would use the Backup/Restore API https://lucene.apache.org/solr/guide/7_5/making-and-restoring-backups.html <https://lucene.apache.org/solr/guide/7_5/making-and-restoring-backups.html>
Alternatively, you could create collection B, using same configset as A, stop solr, copy the data folder and start again -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 14. des. 2018 kl. 07:46 skrev Lei Wang <wanglei3...@gmail.com>: > > Hi guys, > > Currently I am running a 2 nodes cloud of Solr 7.5, I already have a > collection named A and it worked fine with 20GB index Data, while I want to > create a collection named B and want to copy index data from A. > So in Solr5.5, I just copy index folder from A and renamed to B. restart > solr cluster, collection B will be register successfully to solr, and > related data will be pushed to zookeeper(leader info etc). > In Solr7.5, I assume because of > https://issues.apache.org/jira/browse/SOLR-12066, index folder B will be > deleted since no state.json info about collection B can be found in > zookeeper, > > So my question is what should I do If I want B can register to solr cluster > successfully other than folder be deleted? > > I have tried to set legacyCloud to true, and B can be registered to Solr > cloud successfully. collection B status data will be pushed into > /clusterstate.json > <http://10.58.91.47:8081/search/admin/zookeeper?detail=true&path=%2Fclusterstate.json> > , > I have to call MIGRATESTATEFORMAT first then remove legacyCloud or set it > to false. > > So if they is any other solutions for this case? > > Looking forward your response. > > Thanks, > Lyle
